yashsingh1/xdaforums huggingface dataset:
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
I've had a few users who got stuck at "Phone is starting..." and either it just stayed like that, or looped back to bootanimation, at least one each enchilada & fajita, and I'm trying to figure out what the deal is. For most people in the Telegram chat (that's really the best way to get in touch with me, I don't have the time to sign in here and lurk regularly) who have been through the v7.12 testing round last month before I scrapped the release, there were no problems updating through progressive test builds up to v7.13 release.

But it could also be because they've all had updated firmware.

I tested on fajita, wiping it and installing the official v7.11 release (to both slots) on top of OOS 11.1.2.2 (on both slots), with an old copy of NikGapps Basic (so not current, and not even the smaller "core" package) and even flashing the *shudder* old official TWRP 3.5.2_9-0 installer, and old magisk v23 release (non-canary)... set things up, restarted a couple times, let google apps update itself, that kind of thing...

Then ran Settings > System > Updater, installed the 7.13 update, and it restarted and came right back up without a problem. I cannot seem to ever reproduce these show-stopping problems people have, and it kinda makes me feel terrible that I don't have any way to help because I don't have the problem in the first place to test fixes for. :/

Going to recommend that people download the full 11.1.2.2 OTA zip (linked in post #2!) and follow the firmware update procedure as described in https://wiki.lineageos.org/devices/fajita/fw_update if they have the "Android is starting..." loop problem, and see if that helps.

____

Update: Yep, that was it. Use current firmware, people.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
[info added to posts #1 & #2]
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] samsz:
Hello, I'm trying to install this crDroid ROM (over OOS 11.1.2.2), but I have problem with one of the first instruction:

Where can I find this "matching crDroid boot.img"? I've extracted boot.img from crDroid.zip's payload.bin file, but when I executed "fastboot flash boot boot.img", I got "fastboot: error: boot partition is smaller than boot image".
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
It's attached to the second post, but... what you did should have worked (assuming you used the actual file paths and didn't have more than one boot.img for a different device kicking around there), that's rather strange.

Should be 64MB. If it's not, it's likely either the wrong boot.img or it's compressed still somehow.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] samsz:
I double checked that this is for sure the correct boot.img extracted from crDroidAndroid-11.0-20211231-fajita-v7.13.zip (funny thing, it has exactly the same size as the one attached to #2 post, but it's not exactly the same in content, as some bytes differ).

In the end I went back to the method that I'm familiar with, and flash it all via TWRP. I even managed to enable volte/vowifi, so it's a full success. :)

First impressions are great - it's way faster and responsive than OOS 11.1.2.2, battery lasts for longer, and I love all those little improvements and customizations. Thanks for doing a great job making this ROM. :)

One cosmetic issue that I found (and I don't know if this is the right place to report it, but couldn't find other) - in crDroid settings there is an option to replace vowifi icon (it hides volte icon, if vowifi is available), but if this is switched on and airplane mode is enabled, both volte and vowifi icons disappear, instead of just showing vowifi icon.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
Wish I could take any credit for the ROM itself or the features it provides (that is, the stuff in crDroid Settings), but I'm not on the core dev team by any stretch; just the maintainer for these two particular devices...

...and of course THAT is all basically thanks to the LineageOS folks upon whose device & kernel trees I'm building. Little bit of curating, tweaking, one or two original contributions, but mostly I'm just trying to make sure I've got something that works on my phone for as long as the thing keeps ticking.

...

There I go not being able to take a compliment.

THANK you. :) And please be aware that I'm standing on the shoulders of giants here; lots of people smarter than me make it all possible.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] jeanxx:
Ive tried installing v7.13 and 14, with and without magisk, with and without custom twrp and custom recovery and with each one, same result > boots up just fine > gets to logo > logo disappears > BLANK SCREEN. Volume keys work, Power button and menu works, can see navigation keys momentarily. Other than that, phone is absolutely blank. Any Ideas on a resolve?

Please and thank you.

Also, updated all to OOS v11.1.2.2 firmware

Update*: Figured it out. Apparently the firmware on OP website was either bad or not the updated version as they said it is. Got the firmware updated and all is good :)
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] jeanxx:
Im no mathematician, but im pretty sure dash charging wont take 15 hr to fill the battery.

View attachment 5525977
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
Yeah, this is kind of a "damned if you do, damned if you don't" thing.

There's a kernel commit I reverted because it was generating logspam (and there's enough of that already because of our broke-ass prebuilt vendor). However, I should probably just leave it, since reverting it leads to the garbage data about time remaining while DASH charging, as you've so aptly demonstrated.

I never use the DASH charger since it's a great way to kill your battery's longevity, but... I get the appeal.

I'll probably just un-revert it and get more reliable charge info when using DASH charger, at the expense of logspam.

Can I recommend MCD kernel in the meantime? Mr. Danny is a wonderful fellow and does excellent work there; you won't be disappointed.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] jeanxx:
The charge remaining isnt much of an issue for me because I know that the most it takes is an hour to fully charge so timing wise, I know what to expect. I just wanted to bring it to attention just in case it wasn't known.

The major issue I have at this point is the annoying fingerprint icon displaying that I commented on in telegram.

The fingerprint will randomly display when going in and out of apps and will stay on the screen regardless of the dialogue ever being called or not. So when it shows up, pressing on it or hitting back does nothing. But if I slide the notification drawer down, it goes away. But only for a short time as, if I leave apps back to home screen or sometimes even go into apps, the fingerprint icon randomly shows back up.

I can try to get a screen recording if you would like to see what is happening.

This is on a clean install of v7.14
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
Are you, by chance, using AppLocker? And/or FaceUnlock? Try removing FaceUnlock, and removing all apps from AppLocker & see if the rando FOD icon goes away. I'm not sure why it's such a mess sometimes, but.. apparently some of the features that the actual ROM devs have added don't play well with all devices, unfortunately.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] jeanxx:
No face unlock and no applocker. I even turned off the animated blur effect as I know that sometimes causes problems. And it worked for a short while, but then started back up. And as time goes on, its progressively getting worse.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] tolhol:
does anyone know how to add lhdc support?
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
Large Hadron Dingleberry Collider?
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] tolhol:
LoL). Nope. Lhdc is Bluetooth codec.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] fierogt42:
Latest build through updater soft bricked my ROM. Would not boot. Lost ADB too. Could only do fully factory reset which allowed booting to the Android setup wizard, which then hangs and reboots system after clicking "start". This is wack.

Full wipe and reinstall, and everything is good but GPS is still not working right. I can get a lock using a GPS analysis app, sometimes Maps or Waze but some other apps aren't able to see location (McDonald's for example. Junk I know, but location should work).

Update: Dirty flash to Carbon ROM fixed it. Will try dirty flashing back now... very strange.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] AndrÃ©_Droid:
can I OTA update from 7.11 to 7.14 without any hiccups?
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
Good question... can't remember if this was answered in the Telegram group already or not, but... if, by "OTA Update" you mean using the built-in Updater, then... the answer is kind of "it depends".

- IF you're already on 11.1.1.1 or 11.1.2.2 firmware (11.1.2.2 recommended), and

- IF you're rooted with Magisk, and

- IF you've got a reasonably well-supported GApps package with a working addon.d OTA survival script installed (recent/latest releases of MindTheGapps, OpenGapps pico or nano, NikGapps core/basic/omni plus some addons should all be okay, but I don't test all of them -- I'm a MinMicroG "standard" package kind of guy myself), and

- IF you're not trying to preserve TWRP or some other custom recovery, then...

Yes, it should go pretty smooth to just OTA update.

I recommend adding the "Caffeine" QS tile and long-press it until it turns on with the infinity "∞" symbol below it so the phone doesn't go to sleep; the kernel tries to save power when the screen is off and it'll take FOREVERRRRRR.

So to rectify things if you don't meet all those "IF"s:

- you can follow instructions for updating firmware (remember you don't need to format, you can just "dirty update" firmware by flashing the full OOS zip followed by the ROM zip before rebooting back to recovery from TWRP, or you can do it with the extracted boot, dtbo, system, and vbmeta img files using the instructions linked in the LineageOS wiki in post #1),

- you can flash Magisk from recovery to make sure the OTA Updater app will work (it seems to have an accidental dependency and will fail if you're not rooted with Magisk specifically),

- maybe before you try updating to any newer versions of crDroid, you should back up your stuff, reboot into TWRP, mount the system partition, and go look in /system/addon.d/ (3.5.2_9-0) or /system_root/system/addon.d/ (3.x.x_11-0) and take a look at what shell scripts are in there... usually they're named in a reasonably helpful way, so you can tell if it's NikGapps, OpenGapps, etc... so if you don't still have the zips for it available, you can be sure to download the correct version. Up to you to do your own detective work, however.

- If you want to keep TWRP, then don't use the built-in updater and follow the old instructions. Or, use the built-in updater, then reboot to bootloader, download that unofficial TWRP 3.5.2_11-0 img file I compiled (attached to post #2) & `fastboot boot` it, download the old official 3.5.2_9-0 installer zip, and use the newer TWRP to flash the older TWRP zip installer, reboot recovery AGAIN, and re-flash Magisk if you want to remain rooted.

Once you've got latest firmware & Magisk installed and aren't trying to keep TWRP, the built-in OTA Updater works pretty seamlessly, and will preserve Magisk & most of the recommended Gapps packages with addon.d OTA survival scripts correctly.
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] AndrÃ©_Droid:
awesome!! thanks for the reply. I know where I'm at now👍
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
crDroid 7.15 pushed to OTA and first & seconds posts updated with instructions, release notes, current boot.img attachments, etc. 🎉
[OnePlus 6T  ROMs, Kernels, Recoveries, & Other Dev] Terminator.J:
...

Um. What firmware are you on? And what version of crDroid were you coming from when you started this process?
[Moto G7 Plus Questions & Answers] g422:
Just got phone yesterday from amazon. In my attempts to do so fastboot has either "froze" with 3 dots, nothing, or errors like unknown command and a couple others. Ive done this before with previous moto phones. Used moto instructions and other guides and no luck. So any help is appreciated.
[Moto G7 Plus Questions & Answers] sd_shadow:
what does getvar all say

fastboot getvar all
[Moto G7 Plus Questions & Answers] g422:
(bootloader) kernel: uefi

(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200929

(bootloader) product: lake

(bootloader) board: lake

(bootloader) secure: yes

(bootloader) hwrev: PVT

(bootloader) radio: TMO

(bootloader) storage-type: eMMC

(bootloader) emmc: 64GB SAMSUNG DH6DAB RV=08 PV=02 FV=0000000000000002

(bootloader) ufs: N/A

(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12

(bootloader) cpu: SDM636 1.0 (2)

(bootloader) serialno: ZF6523S7H9

(bootloader) cid: 0x0032

(bootloader) channelid: 0x1b
[Moto G7 Plus Questions & Answers] sd_shadow:
Cid should be good (bootloader) cid: 0x0032

There should have been several more lines of data?

Try updating adb files
[Moto G7 Plus Questions & Answers] g422:
Have latest platform tools now the

fastboot getvar is stuck where it labels cpu
[Moto G7 Plus Questions & Answers] sd_shadow:
Try rebooting pc and change usb ports
[Moto G7 Plus Questions & Answers] g422:
It just gave me the serial no under cpu so she is just slow as hell im gonna let it go for awhile see it gives more info than before
[Moto G7 Plus Questions & Answers] g422:
Okay so i restarted used different usb port and different usb plug.

Fastboot getvar showed me what i posted but is hung and has been for 20 mins.
[Moto G7 Plus Questions & Answers] youzi0335:
i'm the same one and just finished unlock, first had the same problem with you.

my solution is change to another computer.

your pc has compatibility issues with the phone.

just started with my dell laptop G7, when move to tower 5810 it is ok.

unlock/flash recovery/install rom, there are always issues appears on the laptop, but it never shown on the desktop.
[Moto G7 Plus Questions & Answers] g422:
Yeah thats what im thinking as well. Im just glad to know it is unlockable. Looks like i have to rebuild my old pc.
[XV6700, PPC-6700 General] tek2tirado:
so im on my friends comp that runs vista cuz my pc got ****ed up

i dl buildos and got everything runnin ....built a rom but when i try 2 flash i keep gettin errors sayin it wasnt made for this device??

ne one else ever had this problem

ne one have an idea of how 2 fix it?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Terminator.J:
Notes:

- crDroid 7.x (based on Android 11 & LineageOS 18.1) is no longer being maintained. Google has End-Of-Life'd AOSP 11 and will be not releasing any further security patches for it, LineageOS will no longer be updating the lineage-18.1 branches, and the crDroid dev team have EOL'd our 7.x branches as a result.

- 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.39 - Final release - February 2024 ASB release notes/changelog:

Changelog since v7.38 (21 January) official release:

- Merged February 2024 Android Security Bulletin from upstream.

- Whatever the ROM dev team changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 14).

- 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)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] shiftyHungary:
Looking forward on this one, thank you for the effort!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] gray_wolf:
Hopefully android auto and face unlock are working. Thanks in advance.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] MaWalla99:
Can't say anything about Android Auto, but Face Unlock works just fine!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] gray_wolf:
Great, will test and report about the android auto and overall Rom. Thanks again.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] XiaoAk:
DC dimming seems to be missing
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] spartan121:
Welcome back team with a11...even with initial build rom is so stable , like this rom simplicity with so many customisations thankyou:)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] spartan121:
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
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] DRAKOITYU:
what gapps
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] spartan121:
I personally used nikgapps...may be all are compatible
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] gray_wolf:
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.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] boggdy:
Anyone else having issues with GPay? I'm using Magisk, hidden, and GPay still won't work.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] tomasz-c:
Is it possible to update crDroid from 6.13 to 7.2 without data formatting (keeping application and data)?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] mahroze:
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
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] coomac:
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.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] SzymonL:
Quick questions, this rom have smart charging feature?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] not_the_droid_ur_lookin4:
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.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] optimumpro:
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.
[Asus ZenFone 4 Max Questions & Answers] flesherjeremy:
I recently deleted my stock rom and twrp off of my rooted asus 4max. I cant get adb to detect my device cause I'm stuck on the bootloader and fastboot options and cant access developer options to revoke usb debugging authorizations please if anyone can help.
[Asus ZenFone 4 Max Questions & Answers] 5thjunior:
boot into bootloader, flash recovery, ex. fastboot flash recovery recovery.img, after that boot into recovery and flash update package for your phone.