[ROM][CrDroid][11][UNOFFICIAL][RAV*/SOFIA*][7.X]

Search This thread

designlab

Member
Mar 19, 2009
35
10
Puerto Vallarta
designlab.com.mx
Hello, awesome ROM but i cant seam to find the right gapps for it got magisk working as well but with the gaps it just hangs on Rom logo, i've tried the following:

open_gapps-arm64-11.0-micro-20201116-TEST-FIXED.zip
open_gapps-arm64-11.0-pico-20210130-TEST.zip
NikGapps-Addon-11-AdAway-signed.zip

this installed via TRWP as well as visa sideload, anyideas?

Thanks
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
Hello, awesome ROM but i cant seam to find the right gapps for it got magisk working as well but with the gaps it just hangs on Rom logo, i've tried the following:

open_gapps-arm64-11.0-micro-20201116-TEST-FIXED.zip
open_gapps-arm64-11.0-pico-20210130-TEST.zip
NikGapps-Addon-11-AdAway-signed.zip

this installed via TRWP as well as visa sideload, anyideas?

Thanks
I have a build v7.4 with Gapps built in. Check my AFH account.
 
  • Like
Reactions: designlab

ironster

Member
Dec 22, 2013
13
3
BE3pE0l.png


Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned

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


Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

First time installation:

  • Flashing:
    1. Extract the zip and open a shell with ADB and fastboot.
    2. Reboot your device into fastbootd mode.
    Code:
    fastboot reboot fastboot
    3. Flash boot, system, product, and vbmeta.
    Code:
    fastboot set_active a
    fastboot flash boot boot.img
    fastboot flash system system.img
    fastboot flash product product.img
    fastboot flash vbmeta vbmeta.img
    4. Wipe userdata.
    Code:
    fastboot -w
    Gapps:
    1. Fastboot boot TWRP
    2. Flash Gapps arch64 version 11
    3. Reboot
    Magisk:
    1. Boot into TWRP
    2. Flash Magisk vs. 21.1
    3. Reboot



Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel https://github.com/Odin1101/Project-Sofia/tree/Upstream-test

Download: https://androidfilehost.com/?fid=17248734326145729881


Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Device support Telegram link: https://t.me/joinchat/0IkIqVQMwM45MDZh

Thanks to the following devs and contributors
@bcrichster
@Beetle84
@asineth
@gearsofwar567
@kjjjnob

Special thanks:
@vache
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.890s]
writing 'system_a' 1/3...
OKAY [ 2.640s]
sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.996s]
writing 'system_a' 2/3...
OKAY [ 2.557s]
sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.413s]
writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
finished. total time: 50.493s

Thats what happens when I try to flash system. Then I get boot loop. I'm XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5 as stock.
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.890s]
writing 'system_a' 1/3...
OKAY [ 2.640s]
sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.996s]
writing 'system_a' 2/3...
OKAY [ 2.557s]
sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.413s]
writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
finished. total time: 50.493s

Thats what happens when I try to flash system. Then I get boot loop. I'm XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5 as stock.
Make sure you have full fastboot/adb tools installed on your computer.
 

TaZeR369

Senior Member
Aug 28, 2016
199
58
Fresh install no gapps, I'm unable to get the bluetooth to play media, and there is a constant error upon any headset pairings "Problem conneting, please turn off and back on" which of course fixes nothing. It will however play phone sound in this errored state if the media switch is unselected, however unselecting the calls will cause immediate disconnect.

I've played around with all the stuff in developers settings including trying the new Gabeldorsche stack to no avail, when I check for the usual options of codecs and frequences to play its all greyed out leading me to believe perhaps the problem is with the Bluetooth Midi Service? Perhaps someone has been able to fix it or has any ideas?

For now after a day of testing I can say bluetooth has been the only problem, everything else is working very well, I love the features sch as LED control, wish this could be fixed.
 
Last edited:

Rondeau79

Senior Member
Jun 19, 2016
353
340
Fresh install no gapps, I'm unable to get the bluetooth to play media, and there is a constant error upon any headset pairings "Problem conneting, please turn off and back on" which of course fixes nothing. It will however play phone sound in this errored state if the media switch is unselected, however unselecting the calls will cause immediate disconnect.

I've played around with all the stuff in developers settings including trying the new Gabeldorsche stack to no avail, when I check for the usual options of codecs and frequences to play its all greyed out leading me to believe perhaps the problem is with the Bluetooth Midi Service? Perhaps someone has been able to fix it or has any ideas?

For now after a day of testing I can say bluetooth has been the only problem, everything else is working very well, I love the features sch as LED control, wish this could be fixed.
What build number and date are you using?
 

TaZeR369

Senior Member
Aug 28, 2016
199
58
Last edited:
  • Like
Reactions: tinbilly

yknip

Member
Jan 4, 2015
15
5
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.890s]
writing 'system_a' 1/3...
OKAY [ 2.640s]
sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.996s]
writing 'system_a' 2/3...
OKAY [ 2.557s]
sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.413s]
writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
finished. total time: 50.493s

Thats what happens when I try to flash system. Then I get boot loop. I'm XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5 as stock.
From linux to my 2041-4 I received this same error (FAILED...).
me@box:~/phones/sofia/ROMs/CrDroid-v7.4$ sudo fastboot flash system system.img
did the trick.
 

Psyb3rN4ut

Member
Mar 31, 2021
36
1
BE3pE0l.png


Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned

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


Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

First time installation:

  • Flashing:
    1. Extract the zip and open a shell with ADB and fastboot.
    2. Reboot your device into fastbootd mode.
    Code:
    fastboot reboot fastboot
    3. Flash boot, system, product, and vbmeta.
    Code:
    fastboot set_active a
    fastboot flash boot boot.img
    fastboot flash system system.img
    fastboot flash product product.img
    fastboot flash vbmeta vbmeta.img
    4. Wipe userdata.
    Code:
    fastboot -w
    Gapps:
    1. Fastboot boot TWRP
    2. Flash Gapps arch64 version 11
    3. Reboot
    Magisk:
    1. Boot into TWRP
    2. Flash Magisk vs. 21.1
    3. Reboot



Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel https://github.com/Odin1101/Project-Sofia/tree/Upstream-test

Download: https://androidfilehost.com/?fid=17248734326145729881


Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Device support Telegram link: https://t.me/joinchat/0IkIqVQMwM45MDZh

Thanks to the following devs and contributors
@bcrichster
@Beetle84
@asineth
@gearsofwar567
@kjjjnob

Special thanks:
@vache
at the step:
fastboot flash system system.img
------------------------------------------------------
target reported max download size of 536870912 bytes
Sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.706s]
Writing 'system_a' 1/3...
OKAY [ 2.518s]
Sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.761s]
Writing 'system_a' 2/3...
OKAY [ 2.535s]
Sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.281s]
Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
Finished. Total time: 50.531s
-------------------------------------------------------------

it fails with >>>

Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
 

Rondeau79

Senior Member
Jun 19, 2016
353
340
at the step:
fastboot flash system system.img
------------------------------------------------------
target reported max download size of 536870912 bytes
Sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.706s]
Writing 'system_a' 1/3...
OKAY [ 2.518s]
Sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.761s]
Writing 'system_a' 2/3...
OKAY [ 2.535s]
Sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.281s]
Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
Finished. Total time: 50.531s
-------------------------------------------------------------

it fails with >>>

Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
Make sure you are using updated adb/fastboot tools. Use full platform tools, not the 15 second installer.
 

yknip

Member
Jan 4, 2015
15
5
at the step:
fastboot flash system system.img
------------------------------------------------------
target reported max download size of 536870912 bytes
Sending sparse 'system_a' 1/3 (458752 KB)...
OKAY [ 14.706s]
Writing 'system_a' 1/3...
OKAY [ 2.518s]
Sending sparse 'system_a' 2/3 (458752 KB)...
OKAY [ 14.761s]
Writing 'system_a' 2/3...
OKAY [ 2.535s]
Sending sparse 'system_a' 3/3 (444840 KB)...
OKAY [ 14.281s]
Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
Finished. Total time: 50.531s
-------------------------------------------------------------

it fails with >>>

Writing 'system_a' 3/3...
FAILED (remote: Operation not permitted)
I had same problem using fastboot from Linux to flash on stock recovery's fastbootd. Solution was:
me@box:~$ sudo fastboot flash system system.img
 

h0miemaru

Member
Apr 25, 2021
13
1
Moto G Power
honestly I was in the same boat you're in. was kinda just following instructions on how to flash a rom without really knowing what I was doing.
my phone was so messed up I couldn't even boot into TWRP. I ended up fixing it though by starting back from square 1. I successfully flashed TWRP and instead of trying anything fancy I just flashed Lineage using the sideload feature of TWRP. none of the other methods would work because I guess I just wasn't knowledgeable enough. but if you basically bricked your device and just want it to boot into an OS try booting into TWRP and using it's sideload feature to flash Lineage. anyway I know this isn't the lineage thread but im juat trying to help you fix your decice. maybe the devs can post a version of crDroid that can be flashed via sideload. sorry for the rant I just know how stressful it can be when you mess up your phone and it won't boot anymore. Give that method a try if you just want your phone to work so you can move on with your life lol.
 
  • Haha
Reactions: griz.droidx

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    BE3pE0l.png


    Code:
    *** Disclaimer
    I am not responsible for any damage you made to your device
    You have been warned

    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


    Features:
    https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

    First time installation:

    • Flashing:
      1. Extract the zip and open a shell with ADB and fastboot.
      2. Reboot your device into fastbootd mode.
      Code:
      fastboot reboot fastboot
      3. Flash boot, system, product, and vbmeta.
      Code:
      fastboot set_active a
      fastboot flash boot boot.img
      fastboot flash system system.img
      fastboot flash product product.img
      fastboot flash vbmeta vbmeta.img
      4. Wipe userdata.
      Code:
      fastboot -w
      Gapps:
      1. Fastboot boot TWRP
      2. Flash Gapps arch64 version 11
      3. Reboot
      Magisk:
      1. Boot into TWRP
      2. Flash Magisk vs. 21.1
      3. Reboot



    Sources:
    ROM: https://github.com/crdroidandroid
    Kernel: kernel https://github.com/Odin1101/Project-Sofia/tree/Upstream-test

    Download: https://sourceforge.net/projects/crdroid-v7-x-sofiar/files/CrDroid-Sofiar/


    Visit official website @ crDroid.net
    crDroid <device> Telegram
    crDroid Community Telegram
    Donate to help our team pay server costs

    Device support Telegram link: https://t.me/joinchat/0IkIqVQMwM45MDZh

    Thanks to the following devs and contributors
    @bcrichster
    @Beetle84
    @asineth
    @gearsofwar567
    @kjjjnob

    Special thanks:
    @vache
    2
    I don't remember what the exact errors were, but I did have a number of them. I took the ostrich approach and ignored the errors... and the phone booted fine.

    You made me laugh! :)

    Ok, I did that and to my surprise - it booted fine! Working on passing safety net with Magisk now. I really appreciate your help and hope this convo helps others going forward. Thank you!
    2
    Thank you for the reply. I see this is for the "Lenovo Moto G Stylus", yet this thread is for the "Moto G Power" (which is what I have). I'm cautious when flashing ROMs, so just want to double-check....
    Yes, it works for the Moto G Power as well. The OP's link was also for the Stylus; the same question was asked and answered in post #4. I have the XT2041-4 and have run the 7.4 and 7.5 ROMs from the download page I referenced. 7.5 has been my daily driver for a while now, and haven't experienced any issues.
    2
    Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
    but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
    I also had the same problem. You will get the ROM animation forever if you are already on Android 11. You must go back to Android 10 in order for CrDroid to boot properly. Just follow the instructions:

    Flashing:
    1. Extract the zip and open a shell with ADB and fastboot.
    2. Reboot your device into fastbootd mode.
    Code:
    fastboot reboot fastboot
    3. Flash boot, system, product, and vbmeta.
    Code:
    fastboot set_active a
    fastboot flash boot boot.img
    fastboot flash system system.img
    fastboot flash product product.img
    fastboot flash vbmeta vbmeta.img
    4. Wipe userdata.
    Code:
    fastboot -w

    I used the file:

    CrDroid-v7.6-20210519-Sofiar-Gapps-IMG.zip

    Gapps are included in this file.

    Thanks to everybody that helped me out. I hope this helps someone else.
    2
    Here's what worked for me on 2041-4 using a gnu-linux box (there were some permissions gotchas):
    0. power up a new out-of-the-box moto g power 2041-4. Follow prompts. Motorola Software Update will automatically download a system update and prompt reboot, after which Motorola Software Update will once again automatically download a system update and prompt reboot.

    1. become developer, enable usb debugging and OEM unlocking; power off, start fastboot mode (hold volume down and power buttons), and connect phone to (linux) box with usb C cable.

    2. visit https://accounts.motorola.com/ and follow instructions to unlock bootloader. Reboot and make sure to enter set up a security pattern, become developer, and enable usb debugging. Motorola Software Update will download and install system update (in my case QPMS30.80-51-8). Reboot to complete installation.

    3. (This step #3 will provide a backup of the stock system; skip step #3 if you don’t want such a backup.)
    a. Power off and restart fastboot mode.
    you@linux:~$ fastboot boot /path-to/twrp.img
    (in my case twrp-3.5.0-0-rav-sofia.img).
    b. Unlock phone’s TWRP screen with your pattern, then backup the Data partition; Super partition; and the rest of the partitions; separately in three backups.
    c. reboot and move the TWRP folder from internal storage to a removable sdcard.

    Note 1: on my device, there were two Super partitions listed: Super (9312 MB) and Super (System, Product, Vendor) (9312 MB); I just backed up the former.
    Note 2: you must backup the Super partition to internal storage, it will fail if backed up directly to an external sdcard!!

    4. Enter fastbootd mode as follows:
    a. enter fastboot mode (with power off, hold volume down and power buttons)
    b. choose ‘recovery mode’ from fastboot menu, press power button to choose.
    Note: the recovery screen displays an android icon with a red warning triangle and the text “No command”. This is not an error!
    c. hold power button 3 seconds then vol up 2 or 3 seconds then release
    d. you see a menu: select enter fastboot with volume keys and power button
    e. you see a screen with “fastbootd” in red at the top of the screen
    f. connect usb cable to computer

    5. unzip your ROM and cd /ROMdirectory
    you@linux:/ROMdirectory$ cd /ROMdirectory
    you@linux:/ROMdirectory$ fastboot set_active a
    you@linux:/ROMdirectory$ fastboot flash boot boot.img
    you@linux:/ROMdirectory$ sudo fastboot flash system system.img
    Note: the above command fails if invoked as normal user!
    you@linux:/ROMdirectory$ fastboot flash product product.img
    you@linux:/ROMdirectory$ fastboot flash vbmeta vbmeta.img
    you@linux:/ROMdirectory$ fastboot erase userdata

    6. reboot phone & setup

    7. root
    you@linux:~$ adb push Magisk-21.4.zip /storage/yourSDcard/
    you@linux:~$ adb reboot bootloader
    you@linux:~$ fastboot boot twrp-3.5.0-0-rav-sofia.img

    Now, from phone’s TWRP screen, install Magisk zip (& gapps or micro_g if you want?)

    Hope that helps!