[ROM][12.1/11][UNOFFICIAL][redfin] crDroid v8.14/v7.28

Search This thread
By:
Advanced…
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
manjaroid said:
OpenContacts or Simple Contacts are a couple options that do some of what you want.

OpenContacts uses its own database that's shielded from Android. It's the most private option I know but the least convenient.

Simple Contacts lets you have it both ways by saving entries on device that you can sync with CardDAV, or store in the Android database for contacts you want to sync with Google.

With any alternative contacts app expect tradeoffs with dialers, SMS etc.
Click to expand...
Click to collapse

Thank you very much. Yes, your suggestions indeed point me to the way to solve my issue. And I did indeed solve it in a similar manner. Here is my explanation of my solution ...

https://forum.xda-developers.com/t/...e-system-administration.3806260/post-88276391
 
  • Like
Reactions: manjaroid
M

manjaroid

Senior Member
Jun 25, 2019
346
161
HippoMan said:
Thank you very much. Yes, your suggestions indeed point me to the way to solve my issue. And I did indeed solve it in a similar manner. Here is my explanation of my solution ...

https://forum.xda-developers.com/t/...e-system-administration.3806260/post-88276391
Click to expand...
Click to collapse
Glad to hear, looks like you came up with a sound solution that doesn't sacrifice much.

I knew there'd be other options but I've only tried those two apps. It's been a while since I made any attempt at protecting contacts or de-Google measures of any kind. My focus on other types of push-back never let up but it hasn't been enough. The situation keeps getting more ridiculous unless we take the initiative.

Thanks for pointing to that thread, it's bookmarked and will be part of my refresher course.
 
  • Like
Reactions: HippoMan
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
manjaroid said:
Glad to hear, looks like you came up with a sound solution that doesn't sacrifice much.

I knew there'd be other options but I've only tried those two apps. It's been a while since I made any attempt at protecting contacts or de-Google measures of any kind. My focus on other types of push-back never let up but it hasn't been enough. The situation keeps getting more ridiculous unless we take the initiative.

Thanks for pointing to that thread, it's bookmarked and will be part of my refresher course.
Click to expand...
Click to collapse
That thread is for the "TeMeFI" app, which is a very useful system administration tool for Android that was created by the author of that thread, "DiamondJohn". I went to that thread to see if the "TeMeFI" utility might be able to help me solve my issue with device-only contacts. And as a result of my discussion there, I learned what I needed to do in order to accomplish that goal.

Through the use of that "TeMeFI" app, it's possible to do a lot of system-level tweaking of Android devices, and the software and the thread itself are very good and helpful resources.
 
  • Like
Reactions: manjaroid
H

hunfatal

Senior Member
Nov 10, 2011
813
586
Budapest
OnePlus X
Google Pixel 5
Sorry guys for the lack of maintining, especially because of the gapps issues in v8/A12, I don't have the time. I've done a build a locally with crgapps but couldn't test it.

I really hope that I will have the time to try it and reinstall my phone at the beginning of April.

Anyone would use it at all? I saw that there are offical builds for v9/A13.
 
Nemoff

Nemoff

New member
Apr 7, 2023
3
0
Hi there,
I am still waiting for an update. And with pleasure I use this wonderful ROM. Thanks to the author.
P.S. V.8/A12
 
Nemoff

Nemoff

New member
Apr 7, 2023
3
0
hunfatal said:
I've updated the ROM on Monday. No commits since then, I will update next time when the April security patches included.
Click to expand...
Click to collapse
Great! I also want to add that for 3 months of using ROM I had no problems. The device works smoothly and without lags. I love everything about this version. Perfect customization. Thank you for support.
P.S. Downloaded your update. Flash through three points in the system as OTA from local storage or ADB recovery?
 
Last edited:
H

hunfatal

Senior Member
Nov 10, 2011
813
586
Budapest
OnePlus X
Google Pixel 5
Nemoff said:
Great! I also want to add that for 3 months of using ROM I had no problems. The device works smoothly and without lags. I love everything about this version. Perfect customization. Thank you for support.
P.S. Downloaded your update. Flash through three points in the system as OTA from local storage or ADB recovery?
Click to expand...
Click to collapse
You can't flash as OTA.

Reboot into recovery and sideload the new build over ADB. Just don't wipe anything, simply dirty flash over it then reboot.

If you have ROOT, you probably lose it, go back into recovery again and reflash magisk (it's important to start the system once before flashing Magisk again). If you don't have root you can skip this part.

And before you upgrade make sure you have backup of everything important, in case something goes wrong.
 
Nemoff

Nemoff

New member
Apr 7, 2023
3
0
hunfatal said:
You can't flash as OTA.

Reboot into recovery and sideload the new build over ADB. Just don't wipe anything, simply dirty flash over it then reboot.

If you have ROOT, you probably lose it, go back into recovery again and reflash magisk (it's important to start the system once before flashing Magisk again). If you don't have root you can skip this part.

And before you upgrade make sure you have backup of everything important, in case something goes wrong.
Click to expand...
Click to collapse
Thank you very much, comrade. Where can I see the log of new changes? Looking forward to further support for this wonderful ROM.
 
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
I'm currently very happily running crDroid-7.25 on my Pixel 5 (redfin) with Magisk 23.0 and TWRP 3.7.0_11.0.

I would like to upgrade to version 7.28, and I want to make sure that I do everything correctly. Could one or more of you confirm that all of the following would be the correct details of the upgrade procedure?

(1) Take a full nandroid backup of my system using TWRP.
(2) Dirty-flash the crDroid-7.28 ROM via TWRP.
(3) Reboot into the OS
(4) Make sure that the bootloader is still unlocked (I think it probably will be).
(5) Reboot back into TWRP.
(6) Re-install Magisk 23.0 (is this actually necessary after a dirty crDroid flash?)
(7) Reboot back to the OS.

Is step 4 really necessary?
What about steps 5, 6, and 7?

Thank you very much in advance.
 
H

hunfatal

Senior Member
Nov 10, 2011
813
586
Budapest
OnePlus X
Google Pixel 5
Step 4 is not necessary, bootloader won't
HippoMan said:
I'm currently very happily running crDroid-7.25 on my Pixel 5 (redfin) with Magisk 23.0 and TWRP 3.7.0_11.0.

I would like to upgrade to version 7.28, and I want to make sure that I do everything correctly. Could one or more of you confirm that all of the following would be the correct details of the upgrade procedure?

(1) Take a full nandroid backup of my system using TWRP.
(2) Dirty-flash the crDroid-7.28 ROM via TWRP.
(3) Reboot into the OS
(4) Make sure that the bootloader is still unlocked (I think it probably will be).
(5) Reboot back into TWRP.
(6) Re-install Magisk 23.0 (is this actually necessary after a dirty crDroid flash?)
(7) Reboot back to the OS.

Is step 4 really necessary?
What about steps 5, 6, and 7?

Thank you very much in advance.
Click to expand...
Click to collapse
Step 4 is not necessarry, bootloader won't lock itself.

Because the kernel is updated/reflashed when upgrading versions, you lose root (as it is not patched by default), therefore Magisk reflash is required.

So, your steps are correct (although I haven't tried TWRP because it wasn't stable at the time I've used A11 so I've used the stock crdroid/lineage recovery), except you can skip (4).
 
  • Like
Reactions: HippoMan
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
hunfatal said:
Step 4 is not necessary, bootloader won't

Step 4 is not necessarry, bootloader won't lock itself.

Because the kernel is updated/reflashed when upgrading versions, you lose root (as it is not patched by default), therefore Magisk reflash is required.

So, your steps are correct (although I haven't tried TWRP because it wasn't stable at the time I've used A11 so I've used the stock crdroid/lineage recovery), except you can skip (4).
Click to expand...
Click to collapse
Thank you very much. This gives me a lot more confidence.

I presume that a crdroid/lineage-recovery-based flash won't do the flashing itself any differently than how a TWRP-based flash would do it.

Just for clarity (in case anyone wants to see correct instructions), these are the steps using TWRP:

(1) Take a full nandroid backup of the system using TWRP.
(2) Dirty-flash the crDroid-7.28 ROM via TWRP.
(3) Reboot into the OS and make sure all is well.
(4) Reboot back into TWRP.
(5) Re-flash Magisk 23.0 via TWRP.
(6) Reboot back to the OS.

If not using TWRP, replace step 1 with some method of taking a full backup, such as maybe with SwiftBackup or Migrate, and then just replace the word "TWRP" in steps 2, 4, and 5 with "recovery".
 
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
HippoMan said:
Thank you very much. This gives me a lot more confidence.

I presume that a crdroid/lineage-recovery-based flash won't do the flashing itself any differently than how a TWRP-based flash would do it.

Just for clarity (in case anyone wants to see correct instructions), these are the steps using TWRP:

(1) Take a full nandroid backup of the system using TWRP.
(2) Dirty-flash the crDroid-7.28 ROM via TWRP.
(3) Reboot into the OS and make sure all is well.
(4) Reboot back into TWRP.
(5) Re-flash Magisk 23.0 via TWRP.
(6) Reboot back to the OS.

If not using TWRP, replace step 1 with some method of taking a full backup, such as maybe with SwiftBackup or Migrate, and then just replace the word "TWRP" in steps 2, 4, and 5 with "recovery".
Click to expand...
Click to collapse
[ NOTE: I posted a question about this here, but then I figured out the answer, so I deleted that post, and this current message supersedes it. ]

I had forgotten that I lose TWRP when flashing crDroid. So the following is the new-and-improved series of steps ...

(1) Take a full nandroid backup of the system using TWRP.
(2) Dirty-flash the crDroid-7.28 ROM ZIP file via TWRP
(3) Reboot into the OS and make sure all is well.
(4) Reboot into recovery. It will now be crDroid's recovery.
(5) Re-flash Magisk 23.0 via sideload.
(6) Reboot back to the OS.

All this worked for me with no problem!

I decided just to keep the crDroid recovery instead of permanently installing TWRP. To perform nandroid backups or restores, I can just do the following ...

(1) Boot into the bootloader.
(2) fastboot boot [TWRP IMG file]
(3) Perform the nandroid backup or restore.

It turns out that TWRP 3.7.0_11-0 can't do sideload on my device. It kills the adb-to-device connection and then errors out. I have no problem with adb push and adb pull with that version of TWRP ... sideloading is the only problem with it.

The crDroid recovery has no problem sideloading.
 
Last edited:
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
I'm running crDroid-7.28 on my Pixel5 (redfin).

Is there any way to tell crDroid to show fewer than 6 status-bar quick-settings tiles? I can't find anything in the Settings which controls this, but maybe I'm missing something.

Thank you in advance for any ideas and suggestions.
 
HippoMan

HippoMan

Senior Member
May 5, 2009
2,160
938
Hippoland
badaas said:
Maybe aospmods can help:

https://github.com/siavash79/AOSPMods
Click to expand...
Click to collapse
Thank you, but I am running Android 11 (crDroid-7.28). It turns out that aospmods only works on Android 12+.

... and if I upgrade to an Android 12 or 13 version of crDroid, I will no longer be able to use Magisk 23.0, and I therefore will have to go down a convoluted, confusing, maddening rabbit-hole of headaches and bootloops due to trying to get a newer version of Magisk to work.

So, perhaps I'm out of luck about reducing the number of columns of quick-setting tiles.
 
Last edited:
Waldemar2022

Waldemar2022

New member
May 22, 2023
1
1

Attachments

  • 1.jpg
    1.jpg
    270.4 KB · Views: 10
  • 2.jpg
    2.jpg
    256.7 KB · Views: 8
  • Like
Reactions: HippoMan
You must log in or register to reply here.

Similar threads

aleasto
[ROM][OFFICIAL][redfin] LineageOS 20
Replies
927
Views
130K
thenad7841
thenad7841
kdrag0n
ROM ❯ PIXEL 5 ❯ OFFICIAL ❯ ProtonAOSP 11
Replies
835
Views
141K
thenad7841
thenad7841
B
[RECOVERY] - TeamWin Recovery Project [REDFIN] [OFFICIAL]
Replies
378
Views
73K
D
Durchmesser
dabug123
[ROM][OFFICIAL][Android 11]ScorpionROM v4.7[Google Pixel 5][Redfin]
Replies
164
Views
44K
G
ghost9640
aleph.mercury
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.8 Sisig |TQA.230405.003.E1 UPDATED Apr 21-2023
Replies
127
Views
15K
aleph.mercury
aleph.mercury

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    H
    hunfatal
    Step 4 is not necessary, bootloader won't
    HippoMan said:
    I'm currently very happily running crDroid-7.25 on my Pixel 5 (redfin) with Magisk 23.0 and TWRP 3.7.0_11.0.

    I would like to upgrade to version 7.28, and I want to make sure that I do everything correctly. Could one or more of you confirm that all of the following would be the correct details of the upgrade procedure?

    (1) Take a full nandroid backup of my system using TWRP.
    (2) Dirty-flash the crDroid-7.28 ROM via TWRP.
    (3) Reboot into the OS
    (4) Make sure that the bootloader is still unlocked (I think it probably will be).
    (5) Reboot back into TWRP.
    (6) Re-install Magisk 23.0 (is this actually necessary after a dirty crDroid flash?)
    (7) Reboot back to the OS.

    Is step 4 really necessary?
    What about steps 5, 6, and 7?

    Thank you very much in advance.
    Click to expand...
    Click to collapse
    Step 4 is not necessarry, bootloader won't lock itself.

    Because the kernel is updated/reflashed when upgrading versions, you lose root (as it is not patched by default), therefore Magisk reflash is required.

    So, your steps are correct (although I haven't tried TWRP because it wasn't stable at the time I've used A11 so I've used the stock crdroid/lineage recovery), except you can skip (4).
    View
    1
    badaas
    badaas
    Maybe aospmods can help:

    GitHub - siavash79/AOSPMods: mixed Xposed+Magisk module for customization of AOSP-based Android 12+

    mixed Xposed+Magisk module for customization...
    github.com github.com
    View
    1
    Waldemar2022
    Waldemar2022
    HippoMan said:
    ... am running Android 11 (crDroid-7.28)...
    Click to expand...
    Click to collapse
    I have version srDroid 7.21 so
    View
  • 24
    H
    hunfatal
    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:

    Flashing Instructions:

    Information:
    • This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
    • This ROM bundles the latest firmware so you don't have to worry about updating firmware beforehand.
    • Gapps included
    • Magisk for root (after first boot) - (Download from here)

    Installation:

    crDroid v7
    • Back up anything you want to keep from your internal storage, because Formatting the data in the recovery formats the internal storage
    • Download the latest recovery image and rom zip
    • Boot to bootloader
    • fastboot flash boot crDroidAndroid-11.0-xxxxxxxx-redfin-signed-v7.xx-boot.img
    • Boot to recovery
    • Format data
    • Sideload crDroid zip
    • Optionally flash any addons:
      • Advanced > Reboot to recovery
      • Sideload the addons
    • Reboot
    crDroid v8
    • Back up anything you want to keep from your internal storage, because Formatting the data in the recovery formats the internal storage
    • For the first install, Android 12 firmware is required from the latest stock ROM
    • Download the latest stock Lineage recovery image and rom zip
    • Boot to bootloader
    • fastboot flash vendor_boot crDroidAndroid-12.1-xxxxxxxx-redfin-signed-v8.xx-vendor_boot.img
    • Boot to Lineage recovery (comes with flashing vendor_boot)
    • Format data
    • Sideload crDroid zip
    • Optionally flash any addons:
      • Advanced > Reboot to recovery
      • Sideload the addons
    • Reboot



    Sources:

    Download:

    Known issues:
    • crDroid v7 (Android 11)
      • Bootloop after changing fonts/theme in the settings
    • crDroid v8 (Android 12)
      • None

    Contributors:
    Visit official website @ crDroid.net
    crDroid Community Telegram
    Donate to help crDroid team pay server costs
    View
    11
    H
    hunfatal
    ROM updated to v7.20 with the latest upstream changes. I've disabled smart charging in this version because it's not working.

    I've also prepared the build (kinda) for A12/crDroid v8, but I don't have time to try it, hopefully I can try it and release it in the next month.
    View
    8
    H
    hunfatal
    Update for crDroid 7.13 available to download.

    Happy New Year for everyone!
    View
    7
    H
    hunfatal
    Changelog for crDroid v8

    2022-09-12
    - Initial release

    2023-04-03
    - Latest upstream crDroid and LineageOS changes
    - Some GApps related fixes


    Changelog for crDroid v7

    2021-11-08
    - Latest upstream crDroid and LineageOS changes

    2022-01-01
    - Latest upstream crDroid and LineageOS changes

    2022-03-13
    - Latest upstream crDroid and LineageOS changes

    2022-04-15
    - Latest upstream crDroid and LineageOS changes

    2022-05-20
    - Latest upstream crDroid and LineageOS changes

    2022-07-31
    - Latest upstream crDroid and LineageOS changes
    - Smart Charging disabled due to issues

    2022-08-25
    - Latest upstream crDroid and LineageOS changes

    2022-12-24
    - Latest upstream crDroid and LineageOS changes

    2023-04-03
    - Latest upstream crDroid and LineageOS changes
    View
    7
    H
    hunfatal
    andybones said:
    Hey man this ROM has been extremely solid. A small issue here or there but nothing too bad by any means. Thank you again for building, and sharing.
    If you do decide to possibly build another ROM, I humbly suggest AICP.
    I have the latest running on my HTC One M8 and it has some really cool features!
    Don't take this as me not being grateful for this ROM though, it really is nearly perfecto.
    I just love variety and trying the different ROMs.
    The inclusion of PixelGapps and more specifically the Pixel launcher really does help to make this so close to stock but with an enormous amount of customization.
    Click to expand...
    Click to collapse
    AICP is in my plans. I want to try it out myself, we will see. :)
    View

New posts