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

Search This thread

designlab

Member
Mar 19, 2009
14
7
Puerto Vallarta
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
330
317
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
11
2
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
330
317
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
120
17
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
330
317
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
120
17
What build number and date are you using?

CrDroid v7.2 Feb 06, 2021, the one downloaded from the first post.


I just noticed you have newer ones on the android file host, I am going to try

CrDroid-v7.4-20210311-Sofiar-Vanilla.zip

Update - Bluetooth seems to work alright with this new build, you really should update the link in the original post.​

 
Last edited:
  • Like
Reactions: tinbilly

yknip

Member
Jan 4, 2015
9
3
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...).
[email protected]:~/phones/sofia/ROMs/CrDroid-v7.4$ sudo fastboot flash system system.img
did the trick.
 

Psyb3rN4ut

Member
Mar 31, 2021
34
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
330
317
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
9
3
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:
[email protected]:~$ sudo fastboot flash system system.img
 

h0miemaru

New member
Apr 25, 2021
3
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.
  • 1
    What build number and date are you using?

    CrDroid v7.2 Feb 06, 2021, the one downloaded from the first post.


    I just noticed you have newer ones on the android file host, I am going to try

    CrDroid-v7.4-20210311-Sofiar-Vanilla.zip

    Update - Bluetooth seems to work alright with this new build, you really should update the link in the original post.​

    1
    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.
    1
    After lots of struggle, I have successfully installed crDroid 7.4 together with nanodroid plus microG, Google Play Store on my XT2041-1. The phone runs flawlessly so far. Below is what I did:

    1. Back to stock rom: Install Stock Firmware on Motorola G8 Power via Fastboot Commands. [The stock rom was put on the slot_B partition >> I am wrong on this]

    2. Install CrDroid [(on slot_A partition) >> I am wrong too. With fastboot set_active a, we have fixed Slot A as the active slot. Hence the ROM would be flashed to the inactive one, i.e. Slot B]. Note: I did get an error message "Not enough space to resize partition" when flashing system.img. To fix this, I flashed product.img then system.img.

    3. Install Magisk: Rooting ( after unlocking bootloader)

    4. Install NanoDroid: NanoDroid Installation Setup as a Magisk module. I did alter the installation to get both Google Play (patched with microG (in-)app-purchase support) and Aurora Store (alongside Aurora Services addon) installed (nanodroid_play=30). Note: I downloaded the stable version here NanoDroid-23.1.2.20210117.zip and edited the configuration file (.nanodroid-setup) right inside the NanoDroid-23.1.2.20210117.zip.

    5. Install microG Installer Revived as a Magisk module in order to get a real Play Store

    6. Set-up MicroG

    7. Install other GMS-dependent apps which, in my case, included Google Maps and Google Earth

    8. Most interestingly, I did get the Blackberry Keyboard working flawlessly on my phone

    That's it. Feel free to share your experience or ask me any question. I am willing to help as much as I can. Thanks for reading.
    1
    2. Install CrDroid (on slot_A partition). Note: I did get an error message "Not enough space to resize partition" when flashing system.img. To fix this, I flashed product.img then system.img.
    Best tip ever! I wouldn't rhink to do this because I didn't think it'd a difference.
    8. Most interestingly, I did get the Blackberry Keyboard working flawlessly on my phone

    Ive heatd about this keyboard, ia it on the mirror apk site.

    What do you like about it compared to say floris keyboard(my nu goto and it respects your privacy altnough in beta its already really sweet for what they're trying to do)

    Being google free for a few years now thanks to microg.

    Other than disablimg notifications, ia there a way to utilize GCM without logging into a google account to use apps like signal and telegram?

    I must say CR has done well i feel from a privacy perspective as it has offered spoofing for as long as i can remember. When many other distros didn't wouldn't or were too blind to its benefits compared to security.
  • 10
    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
    1
    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.
    1
    What build number and date are you using?

    CrDroid v7.2 Feb 06, 2021, the one downloaded from the first post.


    I just noticed you have newer ones on the android file host, I am going to try

    CrDroid-v7.4-20210311-Sofiar-Vanilla.zip

    Update - Bluetooth seems to work alright with this new build, you really should update the link in the original post.​

    1
    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.
    1
    After lots of struggle, I have successfully installed crDroid 7.4 together with nanodroid plus microG, Google Play Store on my XT2041-1. The phone runs flawlessly so far. Below is what I did:

    1. Back to stock rom: Install Stock Firmware on Motorola G8 Power via Fastboot Commands. [The stock rom was put on the slot_B partition >> I am wrong on this]

    2. Install CrDroid [(on slot_A partition) >> I am wrong too. With fastboot set_active a, we have fixed Slot A as the active slot. Hence the ROM would be flashed to the inactive one, i.e. Slot B]. Note: I did get an error message "Not enough space to resize partition" when flashing system.img. To fix this, I flashed product.img then system.img.

    3. Install Magisk: Rooting ( after unlocking bootloader)

    4. Install NanoDroid: NanoDroid Installation Setup as a Magisk module. I did alter the installation to get both Google Play (patched with microG (in-)app-purchase support) and Aurora Store (alongside Aurora Services addon) installed (nanodroid_play=30). Note: I downloaded the stable version here NanoDroid-23.1.2.20210117.zip and edited the configuration file (.nanodroid-setup) right inside the NanoDroid-23.1.2.20210117.zip.

    5. Install microG Installer Revived as a Magisk module in order to get a real Play Store

    6. Set-up MicroG

    7. Install other GMS-dependent apps which, in my case, included Google Maps and Google Earth

    8. Most interestingly, I did get the Blackberry Keyboard working flawlessly on my phone

    That's it. Feel free to share your experience or ask me any question. I am willing to help as much as I can. Thanks for reading.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone