[ROM][OFFICIAL][fajita][11.0_r64]crDroid Android[v7.27]

Search This thread


Mar 24, 2018
I am running into an issue at this step:

Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery (white & purple on black color scheme, LineageOS logo in the middle).

At this stage my phone displays the "boot loader is unlocked and software integrity..." screen and just stays there. Does this mean that the step below didn't work correctly?

If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.

Any help would be greatly appreciated.


Mar 24, 2018
Ok got it installed. Play Store seems to think that I am using a Pixel 6 Pro, is that normal? Do I need to edit build.prop to fix, or is there a better way to do they now? This is preventing me from installing Netflix :/
WIP Updates:
crDroid 7.16 is basically ready to go; real life & family continues to demand most of my time, and doing the needful upkeep in terms of writing changelogs, reviewing installation instructions & notes in the first two posts is the hardest part. I hate it when there's no useful documentation for things, so writing real changelogs & release notes is basically as important to me as the updates themselves. Not much changed from 7.15, current zip is labelled "test 2" but I should probably pull sources again just in case there's been some bug fixes late in the month, and build a release candidate.
Anybody who doesn't want to wait for the official OTA push is welcome to come get the latest test build links from the Telegram group.
crDroid 8.3 is in beta testing as well, whoop whoop! I've been importing the LineageOS lineage-19.0/.1 branch changes as fast as I can, along with the Android 12L merges coming into the crdroid 12.1 branches, and it's already not terrible. Not quite ready for prime time of course, but it's happening! If you want to come help with testing, be sure you back up your data to your computer, update firmware to in both slots, and go join the Telegram channel to download some test zips! We're currently on beta 2; OnePlus Camera v3 is (shockingly) not working yet, so the basic "Camera2" app is in there as well (feel free to test your favorite GCam port for compatibility), audio seems to be working correctly but needs more thorough testing for playback & recording in multiple scenarios, bluetooth seems to be working and standard SBC audio codec is working but it doesn't look like it's using all the capabilities of the QTI bluetooth stack and not using any of the HD Audio codecs/frequencies/bit-depths yet, I've been tweaking status bar & display density stuff so please take a look and see if things like antialiased corners/notch masks are working correctly for you, and as always for fajita users -- please see if UDFPS is working correctly (that's the new Google framework for handling under-display fingerprint sensors, rather than the old Lineage 'FOD' framework, which is deprecated now in Android 12).
Just to reiterate: feel free to stick your head in the Telegram channel while we're still beta testing crDroid 8.x & preparing for an official release. :)
Currently on crDroid 8.4 beta2 (April ASB merged); that's been the focus of my attention.
Sorry that's been taking up my time and I haven't pushed cr7.16 yet. Again, if you want the release candidate or beta builds, come check out the TG channel. :D
  • Like
Reactions: Dafelleant
Okay, finally pushed 7.16... now that everyone's releasing 7.17. Oof.
Anyway, 7.16 out, am gonna start test builds of 7.17 now I guess, whee!

Whoops; I had a typo from tidying up the OnePlusCamera addition, and it accidentally doesn't include OnePlusGallery built-in. The necessary permissions are there, however, so it should work fine to just install the apk from my source repo:
Gitlab - Terminator-J
Or come to the TG group and try out the first test build of 7.17 -- now with 100% more typo corrections!
Last edited:
  • Like
Reactions: ghost baby

ghost baby

Senior Member
Apr 17, 2016
OnePlus 6T
Just installed crDroid and overall impression is FANTASTIC! You did a really good job, ROM is smooth, testing it right now and haven't encountered any bugs.
Never used crDroid before, and the level of customisation is unreal. Thank you for putting your time, energy and knowledge in this.
  • Like
Reactions: Terminator.J
Just installed crDroid and overall impression is FANTASTIC! You did a really good job, ROM is smooth, testing it right now and haven't encountered any bugs.
Never used crDroid before, and the level of customisation is unreal. Thank you for putting your time, energy and knowledge in this.
Thank you! :)
I try hard to do a good job as a maintainer for our devices; but I'd be remiss if I didn't give credit where it was due to the actual ROM team: @neobuddy89 @gwolfu @xNombre and several others I can't remember off the top of my head (go see the official site).


Senior Member
Nov 30, 2010
OnePlus 9
First of, I want to preface with this ROM being really well designed. Great Job!

In one of the previous crdroid builds, I experienced 3 bugs:
1. Fingerprint sticks around on screen after unlock (you and I talked about this before)
2. Sometimes after unlocking already, the screen would freeze and I couldn't do anything until I pulled down the notification tray and hit the settings icon, which would trigger another device unlock.
3. Stopped receiving calls, texts, etc from iPhone users

Just wanted to see if the latest build has resolved these issues or if some may still be an issue.

I just went back to Jaguar ROM last night, but there are things about it that I can't get past currently and want to see what my position will be flashing the latest build of CR?

Thanks for your hard work :)


New member
Jan 24, 2021
I've got somewhat of an odd issue I've not had before. Following every single instruction carefully, but whenever I try and boot, it just spits me into fastboot. I've tried msmdownloadtool, then reinstall, and it does the same. Lineage 19 boots, but 18 does the same as crDroid. I'm installing it with Magisk and Nikgapps core. I'm baffled. Any help?


Senior Member
Jul 2, 2016
OnePlus 6T
I've got somewhat of an odd issue I've not had before. Following every single instruction carefully, but whenever I try and boot, it just spits me into fastboot. I've tried msmdownloadtool, then reinstall, and it does the same. Lineage 19 boots, but 18 does the same as crDroid. I'm installing it with Magisk and Nikgapps core. I'm baffled. Any help?
Hi try with mindthegapp package version. It is booted when i tried crdroid, so give a try,
I've got somewhat of an odd issue I've not had before. Following every single instruction carefully, but whenever I try and boot, it just spits me into fastboot. I've tried msmdownloadtool, then reinstall, and it does the same. Lineage 19 boots, but 18 does the same as crDroid. I'm installing it with Magisk and Nikgapps core. I'm baffled. Any help?
If it's a T-Mobile version fajita (usually has an IMEI silk-screened on the back case and/or single-tray sim slot with the second slot blanked out), you probably need to convert to international firmware first (which involves using a patched MSMTool binary with an OxygenOS 9.x payload, and is beyond the scope of the instructions in this thread -- check the two threads about it in the "OnePlus 6T News, Guides, and Discussion" section of XDA).

If you've already *tried* flashing lineage-19.1 or crDroid 8.x, then you need to flash the prebuilt OxygenOS vendor partition image again to vendor_a and vendor_b before trying to install an Android 11 ROM; almost all of them except Syberia were based on the prebuilt vendor, instead of building a vendor partition as part of the installation payload.

That's probably why you COULD boot lineage-19.1 and crDroid 8.x, but not lineage-18.1 or crDroid 7.x.
See the first post section on "Updating firmware" and follow the instructions there (including note about flashing vendor) to make sure you've got all the partitions in good shape for using crDroid 7.x.

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    crDroid v7.27 now live on OTA!
    Updated the "known issues" in post #2 to clarify that our Android 11 builds can't boot with userdata formatted as f2fs due to limitations from prebuilt OOS vendor. You'll need to boot a different recovery and format data as ext4 before proceeding with installation, if you've been experimenting with an f2fs-formatted data partition.
  • 17
    NOTICE: crDroid 7.x (Android 11) is now in maintenance-only release mode, and will probably be End-Of-Life'd soon.
    I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they're blind builds at this point and I don't have time to troubleshoot them any longer.
    Please consider updating to crDroid 9.x (Android 13):
    crDroid 9.x XDA thread - OP 6/6T

    crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.


    A quick glossary and primer on flashing & slots for A/B devices (like ours):

    - "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
    - "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
    - "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
    - "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
    - "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
    - "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
    - Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
    - "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
    - Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
    - The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
    - You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
    - We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
    - The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, and vbmeta. Some ROMs (like Syberia) build the vendor partition from source instead of just trying to work with the existing OEM vendor partition, so they flash that one too when installing. So you definitely need to flash stock vendor before switching from Syberia or another source-built vendor ROM to one like Lineage or crDroid that uses prebuilt.
    - "Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). Unfortunately, OnePlus SDM845 (enchilada & fajita, the OP6 & OP6T) never got a proper source-built vendor bringup by the LineageOS team (upon which crDroid is based). And while Syberia has had source built vendor in Android 11 (possibly 10?), it was only done for enchilada and NOT fajita, it's not trivial to unroll & commonize what they've done to apply to other ROMs, and some of the proprietary files they keep are imported from other similar devices/similar chipsets rather than source-built (presumably because the OnePlus ones are modified in a weird way that the open-source components can't hook into, but still not ideal). So for fixing a lot of the issues we still face with lack of things working quite right, or hardware features not available in custom ROMs (especially compared to newer OnePlus devices like the 7, 8, or 9 series), we're kinda stuck, because you can't just implement it against the stock prebuilt vendor.
    - "Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system partition in custom ROMs for our device are generally built against a particular version of OxygenOS (mostly the contents of the OEM vendor partition), and we've recently had an entire major Android version update come through from OxygenOS. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than the current state of OOS 11, that doesn't matter when you're talking about installing the custom ROM over it. So please, keep an eye out in the release notes for what the recommended/required firmware versions are, and remember to update (procedure below).

    Notes on custom recoveries with OxygenOS 11 firmware:
    - My understanding (from people smarter than me) is that the android-11 tree of TWRP is kind of a mess at the moment. I had made some 3.6.0_11-0 unofficial builds for both enchilada & fajita, but now they don't even seem to boot and I don't know why. TWRP android-11 tree refuses to mount the system partition where it belongs, and so addon.d OTA survival scripts don't work correctly any longer (which means you're hosed if you use NikGapps and update while booted from a TWRP version ending in "11-0", or if you have Gapps installed as a module and forget to reboot recovery & re-flash Magisk after flashing an update from TWRP).
    - Trying to `fastboot boot` an Android 9-based TWRP image (like official 3.5.2_9-0 twrp.img) after installing OxygenOS 11 doesn't work, and will drop you into Qualcomm Crash Dump mode. Don't try to flash it as your boot partion, either.
    - Meanwhile, stock LineageOS-based recovery, for all its shortcomings, has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot" and the background colors go from purple to orange) that lets you flash both slots at once and unlocks critical partitions, while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "real" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, and 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"). But since crDroid is LineageOS-based, it's what we've got, and fastbootd is the best way to update firmware.
    - With all that being said, since it's likely TWRP will only get MORE broken with Android 12 looming large, we're officially only going to support the built-in LineageOS-based recovery & OTA updater moving forward, until things change dramatically. If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that.
    - And on the system update side, applying system OTA updates seems to work correctly using the built-in Updater tool (Settings > System > Updater) both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk v23 canary and MindTheGapps & NikGapps (on tester fajita) and MinMicroG "system" install package on my daily driver enchilada.
    - ...however it has an accidental dependency on Magisk, due to things beyond my control upstream in the ROM. Whoops. Won't work if you don't have Magisk installed.
    - FLASHING the old official TWRP 3.5.2_9-0 INSTALLER zip (or newer) on top of OOS 11.x DOES seem to work for now, but you need to be in a recovery environment that allows you to flash that installer in the first place (either by booting into an already-installed TWRP recovery before updating firmware, or by having an Android 11 compatible recovery boot.img to be able to `fastboot boot`). I don't know if it'll keep working in Android 12 or with crDroid 8.
    - Look, if you really want to stick with TWRP, I don't blame you. I made bootable Android 11 compatible TWRP images for enchilada & fajita back at 3.5.2, and they still work well enough to `fastboot boot` them and then flash the old official 3.5.2_9-0 installer zips. Look at the attachments at the end of post #2. Also, you may want to try one of Siddhesh's custom recoveries; they probably work even better.
    - TL;DR: I prefer TWRP too but current official releases are kinda broken and it's a chore to get the old version installed correctly, so built-in LineageOS-based recovery and Updater app are the supported way to install & update moving forward.

    - Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
    - Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
    - Make sure you've downloaded the most recent full OxygenOS OTA installer zip (, crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
    - Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.

    Let's get started!

    Updating firmware:
    - Reboot to bootloader (with no USB cable connected).
    - If you're not already using the stock (LineageOS-based) recovery, you'll need to `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
    - Reboot to bootloader again (actually loads new bootloader that you just flashed).
    - Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery (white & purple on black color scheme, LineageOS logo in the middle).
    - Tap "Advanced", then tap "Enter fastboot" (the already-selected first option), and color scheme should change from purple to orange.
    - Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ("fastboot reboot").
    - Since those instructions were updated for Android 12, and this is still Android 11-based & depends on using the OxygenOS prebuilt vendor partition contents, you'll also need to run fastboot flash --slot=all vendor vendor.img at the end of the list of commands in the linked LineageOS Wiki article above.
    - If you're only updating firmware and were already on crDroid, you can just "fastboot reboot" which will go back to system. If this is part of coming to crDroid from another ROM, continue with the instructions below.

    First time installing crDroid to your OP6T, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
    - Update to OxygenOS firmware as described above if you haven't already.
    - At the end of that procedure, (re)flash the crDroid boot.img to the `boot` partition of both slots, then reboot to recovery.
    - Once you're rebooted into stock recovery (and lo, it was most purple), ADB sideload the crDroid installation zip. It might prompt you with "Install anyway?" on the phone, so don't just walk away from it.
    - After the adb sideload has finished and the purple menu at the top comes back, hit the back arrow, then choose "Wipe data" (which WILL format internal storage -- you backed up as noted above, right?).
    - Reboot to recovery (causes it to switch slots so any further installations will be on top of the slot that it just installed crDroid into).
    - ADB sideload Magisk and/or any GApps packages you want to use. Please note that any time you install something via ADB sideloading, that the install file is technically renamed "sideload.zip" in transit by the ADB protocol, which might cause problems with installers that try to get too clever for their own good and alter behavior based on renaming the installation zip (like MinMicroG), so you might have to get even MORE clever with changing up installation order (like flash MinMicroG/GApps before Magisk so it won't install as a module. I dunno, talk to the package installer authors to get them to just build multiple packages or talk to the LineageOS devs to allow you to decrypt internal storage, copy stuff to internal storage via MTP, and install stuff from internal storage like a proper custom recovery (or at least maybe `adb push` to an unencrypted temp dir in the data partition).
    - Reboot system.
    - ???
    - Profit!

    OTA updating from Updater app with OOS 11.x firmware (recommended):
    - This is the preferred way now. You just go to Settings > System > Updater, and... install an update. It processes addon.d OTA survival scripts correctly (tested with Magisk, MinMicroG, MindTheGapps, and NikGapps).

    - Please note that there's currently an accidental depencency on Magisk being installed for this to work. I don't know if this will get fixed; that's definitely above my pay grade. This appears to have been fixed; huzzah!
    - If you're trying to do a "Local Install" of the downloaded zip, please note you NEED to download on a computer & transfer to internal storage via USB cable; downloading files from an app on the phone associates it with a particular app thanks to Android 11+ Scoped Storage/SAF bull**** and will cause the file to be unreadable to the updater app process.

    -- Old TWRP-based instructions below the fold (not recommended, but keeping for historical value... probably not accurate but I'm not going to update them more) --
    OTA updating from TWRP with OOS 11.x firmware:
    You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
    - Boot into TWRP recovery.
    - Choose install, then select crDroid.zip, select additional zips, choose the TWRP installer zip, then slide to confirm flash.
    - Reboot recovery.
    - Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
    - Please keep off of the grass, shine your shoes, wipe your... dalvik.
    - Reboot system.

    OTA updating from TWRP with OOS 10.x firmware:
    - Don't. Update firmware to first.

    Reporting bugs:
    I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
    - Logs/screenshots/recordings or it didn't happen. Either the built-in Matlog app, or Syslog (free, open source, available on Play store and F-droid) are your friends here.
    - I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
    - I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
    - Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.

    It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
    - didn't do a clean flash.
    - aren't using the built-in kernel.
    - are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
    - immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
    - are running decrypted.
    - re-locked your bootloader for some reason... you're on a custom ROM; don't do that.

    crDroid Website - Download here!

    Donate - Support development!

    Telegram Oneplus6/6t group - Share your best cat pictures!

    Source Code:
    - Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/11.0
    - OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/11.0
    - hardware/oneplus/ HALs: https://github.com/crdroidandroid/android_hardware_oneplus/tree/11.0-op6
    - Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/11.0
    - crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being actively developed, and I don't know how long someone on the dev team will keep merging monthly security updates. I'll try to keep building releases as long as there are updates, but all my limited time is focused on 9.x/Android 13 bringup now. We're in maintenance mode now, so any outstanding bugs are likely to just remain for perpetuity.
    - Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
    - Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
    - Requires OOS firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
    - Tested against latest Magisk 24 (with zygisk instead of magiskhide), works well.
    - No there won't be official builds with inline GApps; please don't ask.

    crDroid 7.27 - February 2023 ASB release notes/changelog:
    Changelog since v7.26 official release:

    - Merged February 2023 Android Security Bulletins from upstream.
    - Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13).
    - No changes to device-specific files.

    Known issues:
    - If you use App Lock and/or Face Unlock, you'll likely run into issues with the FOD circle view starting to flicker randomly into view when it shouldn't be there (like it's not dismissing properly because one part of the security handling is fighting with or doesn't notify the other part that it's done and doesn't need to try to accept a fingerprint any longer). As a knock-on effect, this will also cause "Disable Night Light when FOD is visible" to freak out. I have one person who doesn't use either report that they were getting the random FOD circle anyway, so... if you're having this problem, please make sure you've given MatLog permission to manage files so that it can actually save logs to internal storage and capture a logcat & send it to me. Logs or it didn't happen, etc etc.


    - No f2fs-formatted userdata support, sadly. Doesn't work with the prebuilt vendor partition required for this version of Android. You'll need to reformat data to ext4 before being able to boot (you can fastboot flash the crDroid 8.x or 9.x boot.img if you need a recovery that will let you choose).
    - Google Hotword recognition might be kinda broken right now (on more than one custom ROM/device, not just us), and may cause some screw-up that prevents microphone audio from being allowed to go anywhere else if it's enabled.
    - If you are stuck at "Android is starting..." looping endlessly, then press power, reboot to bootloader, and follow the instructions for updating firmware to OxygenOS in the first post. It doesn't wipe data, you shouldn't lose anything.
    - Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.

    Helpful links:

    Download ROM

    Android platform tools (adb & fastboot)

    OxygenOS Full OTA

    Firmware update instructions (LineageOS Wiki)

    (Please note that since crDroid 7.x/Android 11 for this device depends on the prebuilt OxygenOS vendor partition, you'll also need to add fastboot flash --slot=all vendor vendor.img to the list of commands in the instructions, just before the final fastboot reboot.

    MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)

    Magisk (use latest)

    Official TWRP 3.5.2_9-0 install zip (good luck)
    (Posting in all 4 threads -- OP6-cr6, OP6-cr7, OP6T-cr6, OP6T-cr7)
    Jeez, it's been almost another month. I'm really sorry I haven't been able to kick out a release for June; I did a big old device tree rewrite for cr6 & cr7, and I've been kernel shopping a lot, and trying to get OOSCam integration stable (so close!). It won't even look that much different when it finally comes out, but it's what needed to happen to be able to maintain both Android 10 & 11 (cr6 & cr7) going forward.
    Probably going to require a clean flash to support the changes in priv-app contents for the camera apps to work correctly... but I'll try to keep this kind of thing to a minimum.
    If you want to live on the edge anyway, come join the Telegram channel where all the test releases get linked as I bang on stuff. Life is busy right now, I can't change that and won't apologize for taking care of my family & comrades & real-life stuff first... But I still want to do right by everyone.
    I'm not dead, and neither are releases of crDroid for OP6/6T. cr7 is the way forward for sure (much as I hate Android 11), but cr6 will be back to official status Real Soon Now(TM).
    crDroid v7.8 (July ASB) is up! Check installation instructions in post #1 and update notes in post #2 for more info. Have fun, kids!
    From the 'Better Nate Than Lever' department... new official March build is out, my first release as the new maintainer.
    - Switching to Illusion kernel from AOSiP (the lineage-17.1 based one from before is unlikely to ever be updated with additional nodes from the OOS 10.0 source release, and doesn't support the DeviceSettings customizations we want in A11. meanwhile, Illusion was also LineageOS-based originally, but has more of the goodies from Q added that support the customizations we want, and maintained more frequently), with updated linux-stable security patches and updated wireguard.
    - Reworked the device tree with a much cleaner merge of vanilla lineage-18.1 sources, unofficial bringup patchset from the Lineage gerrit, and commits from crDroid. This is mostly cleaning up under-the-hood to make it easier going forward (because I made a royal mess of things earlier this yeear/late last year).
    - Temporarily removed DeviceSettings (Settings > OnePlus Settings) for now, because it was buggy as heck. I'm still working on it, but you have to remove some Lineage things to replace with it, and I want you folks to have things working right while I figure stuff out.
    - Panel color modes are temporarily gone due to kernel differences, but DC dimming should be working great (in Settings > Display > Livedisplay > Anti Flicker).
    - (Fajita only): FOD should be working again, although I've heard there's some funky business with the fingerprint graphic not disappearing after opening an app with securelocker; swiping the notification shade down and back up seems to clear it.

    Recommended setup (I haven't tested on anything else, so please match this if you're filing bugs):
    - 10.3.8 OOS base firmware or newer (10.3.9 just came out and works well)
    - Official TWRP 3.5.1_9 (adds ability to flash apks as flashable zips if they have the right content, like magisk 22)
    - Magisk v22 if you're going to root (release, beta, or canary - I've been on canary the whole time, works well)
    - I don't use GApps, but happy to take recommendations for which packages work best. I'm using FriendlyNeighborhoodShane's MinMicroG standard package myself, installed to /system.

    Dirty flash from 7.3 should work fine, although you might want to wipe Dalvik since we're changing kernels, and possibly clear storage/cache of the Settings app itself (that's where most of the work has been done).

    No inline TWRP yet in A11; the old method for including it has been removed ROM-side, so not much I can do for now. If you're installing from recovery or doing a clean flash, you'll need to install the ROM zip, install TWRP, reboot to recovery, install Magisk, then install any GApps/MicroG (or not!), wipe Dalvik, and finally reboot system.