Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "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 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).
Prerequisites:
- 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 Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable 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 (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `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 into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6T, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
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 OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, 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.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
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. Syslog (free, open source, available on Play store and F-droid) is your friend.
- 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.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_fajita/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0
Notes:
- 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).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- 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 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
Fajita-specific:
- FOD seems to work kinda, um, crap compared to how it is on OOS 11 firmware. Not much I can do about that, unfortunately.
Common:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
first to test it...just flashing it...hope its better than every 10 rom that are available currently!!!!
It's early in development. They are all going to have that 'new car smell'. Lower expectations. Bare bones but stable is a milestone.
Hello everyone, firstly thanks Dev and team for your efforts developing CRDroid, question... where can I download android 10? Because the website only shows Pie downloads and 10 only says soon. Thanks guys and have a good day.
funnyquill said:
first to test it...just flashing it...hope its better than every 10 rom that are available currently!!!!
Click to expand...
Click to collapse
What's your thoughts?
Sent from my OnePlus6T using XDA Labs
oscarmaldonado said:
Hello everyone, firstly thanks Dev and team for your efforts developing CRDroid, question... where can I download android 10? Because the website only shows Pie downloads and 10 only says soon. Thanks guys and have a good day.
Click to expand...
Click to collapse
go to pie downloads, there you will find a 6.x folder to
All downloaded ready to flash when I get home
Thanks for the rom dev?
Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.
So when I click on "wallpapers" on home screen, it says app isn't installed. So, is there any fix?
oscarmaldonado said:
Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.
Click to expand...
Click to collapse
Looks like there's plenty of options/goodies under the crDroid settings.
Sent from my OnePlus6T using XDA Labs
L22EEW said:
Looks like there's plenty of options/goodies under the crDroid settings.
Click to expand...
Click to collapse
Yes there is, that's the reason I took that screenshot. Happy flashing bud.
Just superb work.. I am casual user.. Plays lot of games, YouTube and online streaming.. Seems pretty solid so far..
oscarmaldonado said:
Let the game begin, I'm almost done restoring everything, clean flash including internal storage. It booted fine, no issues whatsoever, everything is running nice and smooth, wifi, wifi calling, Bluetooth, FP. Thanks Dev. and team.
Click to expand...
Click to collapse
You have the weather on lockscreen option?
Sent from my OnePlus6T using XDA Labs
champagne66601 said:
You have the weather on lockscreen option?
Click to expand...
Click to collapse
No I don't, I just noticed it.
Will it work on Verizon?
L22EEW said:
Looks like there's plenty of options/goodies under the crDroid settings.
Click to expand...
Click to collapse
oscarmaldonado said:
Yes there is, that's the reason I took that screenshot. Happy flashing bud.
Click to expand...
Click to collapse
nikz106 said:
Just superb work.. I am casual user.. Plays lot of games, YouTube and online streaming.. Seems pretty solid so far..
Click to expand...
Click to collapse
Would you guys say this is the most "forwardly progressed" Android 10 ROM as of current?
Causical said:
Would you guys say this is the most "forwardly progressed" Android 10 ROM as of current?
Click to expand...
Click to collapse
With all due respect to other Devs. this is the one I like the most, lots of customizations compared to other android 10 roms, give a try I beat you won't be disappointed. This is my personal opinion. Happy flashing bud.
oscarmaldonado said:
With all due respect to other Devs. this is the one I like the most, lots of customizations compared to other android 10 roms, give a try I beat you won't be disappointed. This is my personal opinion. Happy flashing bud.
Click to expand...
Click to collapse
Yep just opinions is all I ask for, I don't care much for hierarchy, so not necessarily looking for one thing better over another, I just know 10's in the early stages and I'm not even thinking about jumping over yet, I just like to hear what people think.
Causical said:
Yep just opinions is all I ask for, I don't care much for hierarchy, so not necessarily looking for one thing better over another, I just know 10's in the early stages and I'm not even thinking about jumping over yet, I just like to hear what people think.
Click to expand...
Click to collapse
This is the first 10 rom worth staying on after testing the others I went back to pie might actually be on 10 for good now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "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 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.
Prerequisites:
- 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 Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable 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 (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `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 into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
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 OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, 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.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
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. Syslog (free, open source, available on Play store and F-droid) is your friend.
- 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.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0
Notes:
- 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).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- 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 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)
Thanks dev. This is a great ROM
When you say latest fw, you are talking about OOS Pie or H2OS Q?
firebird11 said:
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:
To be defined
First time installing crDroid to your Op6, or coming from another ROM:
- Be on the latest firmware
- Make sure you're running latest TWRP
- Copy GApps and crDroid zip to your internal storage
- Disable your screenlocks
- Boot into Recovery
- Wipe cache,data
- Flash crDroid zip
- Flash TWRP zip
- Reboot to recovery
- Flash GApps zip
- Flash Magisk zip
- Reboot system
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
DONATE
crDroid Website
Telegram Oneplus6/6t group
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 6
Contributors
firebird11, neobuddy89, gwolfu
Source Code:https://github.com/crdroidandroid
Source Code Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LOS
Version Information
Status: Testing
Created 2019-10-16
Last Updated 2019-10-16
Click to expand...
Click to collapse
Any bugs or something not working?
Will try this weekend.
Thank you dev
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
veronesi.n said:
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
Click to expand...
Click to collapse
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
savinjo22 said:
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
Click to expand...
Click to collapse
Sorry I said not rooted ?... I wanted to say that magisk wasn't installed.
i tryed this rom on my htc m8 and i love it and i will try it again on oneplus 6
Is this also implemented already in android 10? TIA
tiga016 said:
View attachment 4847745
Is this also implemented already in android 10? TIA
Click to expand...
Click to collapse
Yes there's some customization settings.
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
backtrack292 said:
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
Click to expand...
Click to collapse
I assume you used the 'Green Box' link in Sourceforge? That always trips people up. That link is the latest ROM across all crDroid devices. (Currently the OP5 'Cheeseburger') Or next time actually read the file name before flashing.
Ignore that Green Box. Just pretend it doesn't exist. Use the links underneath to get the Enchilada downloads.
a new v6 build is up !
october security and statusbar padding are new
firebird11 said:
a new v6 build is up !
october security and statusbar padding are new
Click to expand...
Click to collapse
does it supports signature spoofing?
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
meistr91 said:
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
Click to expand...
Click to collapse
thank you for the suggestion... gone well beyond the link's status by the time i read this (on oos from local update), so may just wait it out for a working twrp solution - been too long since last used OOS anyway!
new v6 builds are up !
firebird11 said:
new v6 builds are up !
Click to expand...
Click to collapse
Can be flashe with oos 10 base ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects.
FEATURES
OneUI 2.0 under Android 10, ported from the SM-A750FN
All G610 variants should be supported
Arm64 with Treble support
Fully deodexed
SIMPLE-KERNEL included, compiled from A600FNXXU5CTB9 sources. Built permissive
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
N20 multi CSC with additional features (call recording, etc)
And many more!
KNOWN BUGS
Light in capacitive buttons for those devices with hardware buttons
Some 3rd camera apps like footej don't work. Whatsapp video calls could be bugged too. If so, use Whatsapp business
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 6.0 (02/12/2020)
More info in 2nd post
INSTALLATION
Vendor partition is required.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
First boot will take much time, be patient
SCREENSHOTS
https://imgur.com/a/Q5Ysvoz
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
Thanks to my testers and @neel0210 for camera rework
And thanks one more time to @SaiFurR for his design work with banner
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM A7 PORT, ROM for the Samsung Galaxy J7
Contributors
Astrako
Source Code: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/tree/simple_q_permissive
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2020-07-19
Last Updated 2020-08-27
H-ROM A7 PORT V6.0 (02/12/2020)
November security patch
Fixed Dual sim detection
Added High Perfomance mode
Setting volume in different apps should be fixed
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: a9f3cacee034142024fd2802eed21b61
Spoiler: Old versions
H-ROM A7 PORT V5.0 (27/08/2020)
Spoiler: Old versions
Firmware ported from A750FNXXU4CTG2. July security patch
Added SIMPLE kernel
Echo in calls should be fixed. Other minor bugs can be present depending the phone/variant
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: 87fc5ef5c031a2f586d762debcf7b3e0
Added a navbar enabler/disabler to the download folder
H-ROM A7 PORT V4.0 (19/07/2020)
Firmware ported from A750FNOXM4CTE3. June security patch
Specifig bugs: echo in calls
GoogleDrive folder
https://drive.google.com/drive/folders/13UG-hdqWU8nud1JCm6DD0vQXAQjeJCVP
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
Reserved
Great job
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
leo31 said:
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
Click to expand...
Click to collapse
Vendor partition is a partition that comes with treble supported phones j7 isnt one of them but with project spaget you can enable treble support on our phone so that it can install treble roms. To get the vendor partition got to this link and download the latest version (spaget x) and flash create vendor 2.0 and you will have a vendor partition.
which kernal is install ? .... i have downloaded h20 rom for g610f but i face some problem such as phone stuck and reboot automatically.... so i need to know whick kernal is installed......
Great work on the ROM
Kindly help with a working SIM Toolkit zip file for this ROM. Or anybody with a working SIM Toolkit zip file can help me with it. Thanks.
HELP! no me deja hacer vídeos llamadas en ws, en j7 prime
won't let me make video calls on
facing random reboot twice on setup screen, now it boot. no flash light on camera (light burst from screen?) like stock oreo.
hyperlapse - wide selfie nor working
i dont even know what is hyperlapse
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Adriano-A3 said:
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Click to expand...
Click to collapse
Don't ask ?... just install the rom and enjoy bro
Mscreams said:
Don't ask ... just install the rom and enjoy bro
Click to expand...
Click to collapse
Bruh
I can't install it please get me a complete manual for install
With spaget x project get bootloop l
Without show logo cant boot
Recovery: Orange Fox
Vendor 2
G610f/ds
use vendor create v1 not v2
yahiaashraf111 said:
use vendor create v1 not v2
Click to expand...
Click to collapse
And don't need change recovery ?
Now it's OrangeFox based twrp 3.4.0
Should install spaget x?
What working :
1. Wifi
2. Mobile data
3. Hotspot
4. Bluetooth
5. Gps
6. Camera
7. Phone
8. Live drawing camera
9. screen recording
10. Almost everything are working well
But, so far i found some 'not so important' bugs :
1. Opening battery usages give me FC.
2. I cant rename, remove files inside priv-app folder, but copying files to folder inside priv-app worked.
3. Removing app which located on priv-app folder using titanium backup, did not removed the apps. After reboot, the apps are there again. (Problem number 2, i cant remove apk inside priv-app)
4. no blue-light filter (i dont use it, so i dont care)
5. Some camera feature not working (hyperlase, wide selfie, front facing camera only support 4:3 size for taking photo, but video are fine). I dont know what is the function of icon at the right side of resolution inside camera (right side of 4:3 icon)
6. Since aod is not working and im not using it, better remove it.
7. Cant change clock style on lockscren (inside phone setting), but fixed by installing lockstar
8. Screen mode inside display setting has no effect at all (even stock rom does not have that feature, so.... No problem at all)
I really love this rom! Why? Because :
1. Battery life is PERFECT
2. Performance? This rom is running perfectly smooth on UI, and also while playing game and opening apps.
3. Multitasking is great
4. Android Q on 2016 device? Hell yeah.
Please fix the 1st and 2nd problem, because i need to replace gametool apk inside priv-app folder.
Installation variant 610mn-16gb
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
RODRI2688 said:
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
Click to expand...
Click to collapse
Hello
Thanks for your help
This installation help isn't for F variant?
SyntaxDroid said:
Hello
Thanks for your help
This installation help isn't for F variant?
Click to expand...
Click to collapse
Really if it could work, especially if you have been making updates from android v6, it is best to start the root from android v8.0 or 8.1, once achieved, try the installation, but if you already come from that version, you shouldn't have drawbacks. Try it, it's really worth it.
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "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:
Spoiler: Show/Hide
- 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.
Prerequisites:
- 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 (11.1.2.2), 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 11.1.2.2 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) --
Spoiler: Show/Hide
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 11.1.2.2 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
Notes:
- 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 11.1.2.2 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.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin 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:
Fajita-specific:
- 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.
Common:
- 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 11.1.2.2 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 11.1.2.2 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)
MaWalla99 said:
Download: coming soon!
Click to expand...
Click to collapse
will this work with verizon?
Tomkumato said:
will this work with verizon?
Click to expand...
Click to collapse
I don't know since I'm not in the US.
MaWalla99 said:
I don't know since I'm not in the US.
Click to expand...
Click to collapse
Thanks
hi dev thanks for this rom i have successfully installed now, so there is a small info i like to share, that is installing any version of nikgapps apart from core nikgapps will result in bootloop or after even format the data, rom will boot but set up screen says it crashed, so i have installed with core version of nikgapps, rom booted successfully. that's all i have info to share now.
Hi dev ROM is working fantastically after installed all the application I used before, so thanks for it, it has enough customization thanks for it too.
Does NOT work on Verizon.
Hi devs i don't know the reason why this happening, the problem is when i change default launcher to nova launcher system ui automatically crashes, i can't specifically pinpoint the reason, but after launching the Paytm app for first time then paytm also crashed so i don't know what to do now. I have attached logcat from matlog so I think I have captured required info.
Thanks for the ROM. Where is the best place to get A11 gapps?
wangdak said:
Thanks for the ROM. Where is the best place to get A11 gapps?
Click to expand...
Click to collapse
nik gapps
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
1 - remove any passwords used to unlock screens - 2 - Backup all your important data, - 3 - Make sure you're on latest TWRP for Fajita and that you have latest OOS firmware, Gapps, TWRP installer and the ROM you want to install (zip files) copied to your "Downloads " directory, then reboot into recovery mode, - 4 - make sure you're on slot A (tap "reboot", tap slot "A" and reboot to recovery again), 5 - tap "Wipe", "advanced wipe" and select " Dalvick Art/Cache", " data" and "system", - 6 - swipe to wipe, 7 - tap "install" and select OOS, then swipe to install, 8 - install TWRP zip file, 9 - reboot to recovery, - 10 - install OOS on the second slot, 11- install TWRP, 12 - reboot to recovery, 13 - install the new ROM, 14 - tap "Wipe", advanced Wipe", "Dalvick Art/Cache" and "Data", 15 - swipe to wipe, 16 - install TWRP and reboot to recovery, 17 - install GAPPS, - wipe " Dalvick Art/Cache and reboot to system. That's it!
autologic said:
hi all,
I'm on fajita with crdroid 5.11 - Android 9.
i'd like to bump up to this thread's version. any tips for how to go about that - step by step?
I assume it would be something like -- update TWRP, update firmware, then flash rom as usual with instructions in first post?
many thanks
Click to expand...
Click to collapse
Boot in latest TWRP
Flash latest OOS 10
Flash CR Droid Zip
Flash Finalize.zip
Flash latest TWRP
Format data -type Yes to confirm
Reboot to recovery
Flash Gapps & Magisk (Optional)
Coming from a different version of Android, format data is recommended. Backup your data before you do this
Hi LiveDisplay color profile doesn't work ,setting a profile ,once you exit it resets back to normal again
Excellent ROM.
Thanks!
Hi dev i attached a video, in which i try to explain a problem, i can't pinpoint say amazon app only having this kind of problem, but i can say irresponsible of which app suddenly ui will have some kind of problem, it will appear from nowhere after that phone will hang and i need to restart the phone or else battery drains very fast. Kindly look into it. I reinstalled the rom two time freshly, even though it having same kind of problem presist, but i really loved one good feature that is finger print working fantastic even after reboot. OS is not crashing and reboot by itself, app also not crashing but suddenly some part is acting wired. Anyway i will upload the video for proof. I have attached gif file as per xda rules.
I have one last idea in my head instead of using app called migrate to take back up of application installed in my phone and restore to newly installed rom. Better use play store to install all app one by one and see there is any difference, i really love this rom thats why i reinstalling freshly again and again to see any difference possible
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
flash713 said:
I've never used micro g a whole lot in the past but I'm all for it now due to the unbelievable amount of permissions apps ask for and while I love Android I'm no Google person either. I flashed 7.2 CrDroid two days ago and didn't install gapps. Then I went back in twrp and flashed micro g and fdroid from (stable) nano droid installer thread here on XDA. Going to read up more about micro g ..etc.. Op, if you are testing anything that has to do with this or anything feel free to msg me anytime. Ill run whatever through everything possible and gather logs if need be and send them to you properly. Thanks for this rom!! Great job!! Always loved CrDroid! Think i 1st used CrDroid back in 2013 or so. Fantastic rom!! My Screen time on 7.2 CrDroid.
Click to expand...
Click to collapse
Yeah I feel you I'm right where you are I think it's time to ditch Google and get a similar setup. Wonder if there's a thread in the 6t section yet? Google still my friend she'll teach me how to set it up, lol
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Features
A quick glossary and primer on flashing & slots for A/B devices (like ours):
Spoiler: Show/Hide
- "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:
Spoiler: Show/Hide
- 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.
Prerequisites:
- 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 (11.1.2.2), 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 (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.
- Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
- 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/enchilada/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 OP6, coming from stock OxygenOS 11.x or another ROM (stock LOS-based recovery):
- Update to OxygenOS 11.1.2.2 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, 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) --
Spoiler: Show/Hide
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 11.1.2.2 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_enchilada/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
Notes:
- 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 11.1.2.2 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 canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 7.30 - May 2023 ASB release notes/changelog:
Changelog since v7.29 official release:
- Merged May 2023 Android Security Bulletin 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:
- 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 11.1.2.2 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 11.1.2.2 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)
Looking forward on this one, thank you for the effort!
Hopefully android auto and face unlock are working. Thanks in advance.
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
Can't say anything about Android Auto, but Face Unlock works just fine!
MaWalla99 said:
Can't say anything about Android Auto, but Face Unlock works just fine!
Click to expand...
Click to collapse
Great, will test and report about the android auto and overall Rom. Thanks again.
DC dimming seems to be missing
Welcome back team with a11...even with initial build rom is so stable , like this rom simplicity with so many customisations thankyou
Screenshot ???
vindipi said:
Screenshot ???
Click to expand...
Click to collapse
This Rom has latest Android security patch of January and for screenshots open and scroll down this website
crDroid.net - increase performance and reliability over stock Android for your device
official crDroid ROM blog
crdroid.net
what gapps
DRAKOITYU said:
what gapps
Click to expand...
Click to collapse
I personally used nikgapps...may be all are compatible
gray_wolf said:
Hopefully android auto and face unlock are working. Thanks in advance.
Click to expand...
Click to collapse
After running the Rom for 5 days now I can confirm that it's very stable and has tons of customization. Unfortunately though android auto is not working. face unlocking, camera, etc works fine. Would appreciate it if you could fix the android auto issue in the future build.
Anyone else having issues with GPay? I'm using Magisk, hidden, and GPay still won't work.
Is it possible to update crDroid from 6.13 to 7.2 without data formatting (keeping application and data)?
MaWalla99 said:
Download ROM
TWRP (use 3.5.0 or higher)
Magisk (use 21.2 or higher)
Click to expand...
Click to collapse
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
mahroze said:
Hey, I have the twrp-3.3.1-18-enchilada-Q-mauronofrio TWRP installed on my Oneplus 6, do I still need to upgrade it to the one which you are recommending? I'd rather go with the one that I currently have and not go through the hassle of updating the recovery. That being said, obviously you would know much better.
Please guide
TIA
Click to expand...
Click to collapse
Twrp 3.3 should work fine with the rom. You can keep using it if you want to. However, there is no extra step to use 3.5 vs 3.3. You have to flash twrp after flashing the rom so you can upgrade to 3.5 by just flashing it instead of 3.3.
Quick questions, this rom have smart charging feature?
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
not_the_droid_ur_lookin4 said:
Firstly, I just want to say this is the most awesome ROM I've tried and i've sat here for a week trying every rom I could get find on the net. It's almost flawless... except for a few hugely killer problems that will sadly make this ROM unusable for me... even though I love it soooo much and if only these things worked... this would be the most amazing ROM ever.
1. After installing GPS doesn't work.
2. When I get a phonecall... I hear the ring... but nothing happens on the screen... so I can't pickup the call. I see after i got a missed call... but i can't answer calls when they're calling... even if I go to the homescreen from whatever app i was using when i got the call... click on the phone icon.... still nothing. Can't answer the call.
3. Text messages simply don't arrive. If I flash the rom back to stock Oxygen OS ... then the text message comes through. But it's a bit late when you're trying to get a verifiaction SMS sent to you to open an messanging app. Can't use the app because i can't get the verification SMS.
If these three things get fixed... omg this will literally be the best ROM ever.
There is a 4th issue... and for me it's important... but it's probably not any fault really of crDroid ROM to be fair...
Very surprisingly... and I just wanted to see if it would work.... kali nethunter for Oxygen OS which is for droid 10 installs over the top of this rom which is droid 11... to much surprise! ...and almost flawlessly... only issue is it doesn't recognise HID interface.
Man... with these 4 things working... this ROM together with nethunter would make for the most badass hacker pentester phone on the planet... save only for the exact same thing on a oneplus 7 or 8 pro.
Many thanks to the devs of this awesome ROM... who hopefully can get 1, 2, and 3 working in the not too distant future... pretty please?
4 is more of a hope and a prayer... but it would be soooo freaking awesome.
Click to expand...
Click to collapse
You have been positing this in more than one thread. This has nothing to do with any rom, and is related to what you are doing with your phone or the phone itself. Telephony is flowless on every Android 11 custom rom for Oneplus 6. And so is GPS, which literally connects in seconds.
First thing you should do is: disable wifi calling, because if your provider doesn't have the feature (or you are not provisioned for it), that could cause your problems. Next, uninstall any mode you might have. Try calling without Gapps.
Also, if you ever used Syberia Rom, you got custom /vendor, which would not work with other custom roms that use stock /vendor. So, you need to re-flash full stock rom onto both slots, which is a pre-requisite for flashing most custom roms. Then follow directions for installing a custom rom.