yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
I installed crDroid 9 a few days ago and it's running great! This is the first time I've used a custom ROM and it's a breath of fresh air compared to the buggy experience Oxygen OS has become. Loving the customization and features in crDroid. @gwolfu, thanks for all the hard work you've put into this! 🙌

A few questions:

Am I correct in my understanding that updating the system to the latest build via recovery simply rewrites the core system files without affecting apps/data? i.e., flashing the latest update won't wipe my apps and personal data?

If so, why is it necessary to sideload GApps again after flashing the update?

If I flash the latest update and then flash GApps afterwards, will I have to reload all my Google data/settings?

I'm thinking about installing Magisk to root my phone. The OTA update process in the first post mentions a Magisk-specific step, but nothing about Magisk in the recovery method. Does that mean Magisk would stay installed and the phone would stay rooted after updating the ROM via recovery?

Let's say I install Magisk after installing the ROM update. To achieve root, would I use Magisk to patch the version of boot.img from when I clean-installed last week's build, or would it be safe to use the latest boot.img from the Recovery folder in the downloads link?

Thanks!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
It's really only required once (someone correct me if I am wrong). I believe this is to make sure both slots (Slot A like Partition A) and (Slot B like Partition B) have GApps. After which you don't need to do it anymore.

As for the second question:, check the first post:

As mentioned above, updating OTA simply installs in Slot B (Like a partition). Keeping Slot A (Your active partition) untouched while your doing the update on the system.

Once the update is done, instead of rebooting which would trigger a switch to using Slot B as your active slot (which has the latest update), you go to Magisk and use the "Install in active slot" option, which extracts the boot.img from the inactive slot with the latest patch, patches it, and slaps it back in place before the reboot, meaning you reboot to the updated slot while maintaining Magisk and root.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
Understood! A few clarifications: I read through the first post, which is what prompted me to ask the questions initially. I was asking about updating via the recovery method since that's what gwolfu recommends, as opposed to the OTA method. In the recovery update method, he mentions re-flashing GApps and I wanted to understand the rationale for that. There's also no mention of Magisk in the steps for updating via recovery.

Having said that, perhaps I misunderstand the first post? Is it implied that OTA is the only option if Magisk is installed?

Thanks for your help!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
It's not the only option no; there's always more then one option, but it becomes your easiest option because elsewise you would have to manually do the process of extracting the boot.img, patching it with magisk, and flashing it again to the updated slot.

In which case you would want to use the latest boot.img available from gwolfu.

I myself did the steps for the first install, then first update I did via recovery and manually installed Gapps a second time on the second slot with the update, and rooted my phone, and any future updates after that I used OTA to preserve my root the easy way.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dengchunzhi:
Dear developer, I used the latest version of crdroid9 android13 developed by you based on the op7 pro. It was built every week on December 26. All the other functions are perfect. I also like it very much. But there is a very fatal bug. My mobile phone is in deep sleep, that is, one or two hours after the screen is shut down. At this time, someone else opens the phone. My device is just ringing all the time, There is no display interface for answering the call. When I turn on the screen and unlock the phone, I don't see the display interface for answering the call, but it still rings all the time. I can't help but worry. However, when you press the power button again, you will find that you have hung up the call, and then turn on the unlock phone to go to the call log. You will find that there is a missed call, What can I do to answer the call and see the call display interface when I am on my mobile phone? thank you! To Developers
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
Got it, thanks! I think I'll do that exact process you outlined (i.e., first update via recovery, then install Magisk, then OTA for all subsequent updates). When flashing GApps to the second slot, do I just run adb sideload gapps.zip again, or will I need to add a flag like adb sideload --slot-b gapps.zip to install specifically to the second slot?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
Just make sure the Gapps follow the update, whichever slot that may be on in that given moment :)

Hypothetically if your current active slot is Slot B, then the update will go on Slot A, so make sure to have Gapps follow that to Slot A. Or vise versa :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
Sorry misread your question, I never specified a slot by going "--slot-b" myself, that may have been a mistake of mine but I didn't have any issues. I think usually the update knows/already did the swap to the correct slot.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
I went through the sideload crDroid update process and flashed GApps at the end (without specifying the slot) and everything installed without issues!

One final question then I'll quit bugging you :)

I installed Magisk and am ready to root the device, but want to clarify which boot image I should patch. Should I use the same boot image I flashed when I did the initial installation of the 12/23 build, or should I use the latest boot image from the Downloads page? I'm guessing I should use the latest image from the Downloads page, but wasn't sure if the one that's installed on my phone got automatically updated as part of the OS sideload update process or if my phone still has the previous boot image installed.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gwolfu:
Build 20221230 is ready

Changelog: https://crdroid.net/guacamole/9#changelog

Download: https://crdroid.net/guacamole/9
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] foomo:
Is there a way to backup and restore the crDroid Settings?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Epic028:
The battery life improved a lot in the newer builds, the oneplus settings added, and there's still a lot of features like smart pixels. One minor issue is the different icon packs don't seem to be applying to most of the quick settings icons.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] foomo:
I'm facing some issues, maybe I am missing something? Please help!

My target setup: crDroid with microG instead of GApps, system F-Droid with privileged extension. No root / Magisk.

Previously I was on OnePlus 7 (not Pro) with exact this setup but I switched to OnePlus 7 Pro because on the OnePlus 7 crDroid isn't maintained atm. Both F-Droid and microG worked without problems on the 7 but it was still crDroid v6.27 and I assume many things changed since.

Problems:

1) cannot install F-Droid as privileged from crDroid recovery

I clean flashed everything after reset with msmtools. firmware, crDroid recovery, crDroid. crDroid started and everything seemed to be okay. Now I tried to install the ZIP provided by F-Droid (https://f-droid.org/de/packages/org.fdroid.fdroid.privileged.ota/) with adb sideload from crDroid recovery. Changed nothing in the system, got stuck here and installed it as non-system from crDroid. Isn't it possible to flash another zip? Instruction says it works with gapps, so I don't understand why it doesn't work with F-Droid. The problem is reproducable. Any ideas? Can this ROM be installed with TWRP? crDroid 6 worked with TWRP. Could TWRP solve at least the issue with ZIPs?

2) microG is not working

Installed microg from F-Droid (microg.org repo), passed everything in self-check. Enabled everything except Google Account which isn't needed at all. Not one app which uses cloud messaging or google services seems to react to microg, still 0 registered Apps in microG's cloud messaging. Apps which should work with microG failed with error "$app won't run without Google Play services, which are missing from your device.". I don't know if its really necessary but SafetyNet also fails. SafetyNet seems like a firmware problem and not a problem with microG, at least thats the info after research in microG forums. The error is "cts profile does not match". This error also was on my OP7 but there every app worked just fine. Any ideas why microG isn't working at all on crDroid 9?

I know that this could also be some microG problem which should be asked in microG forums but it seems to me like at least some issues are with crDroid so maybe some here has an idea.

Thanks in advance!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] griess543:
You can get Widevine L1 on all custom ROMs. You just have to get L1 working on rooted OOS 11, then when you update to a custom ROM you should keep L1. Here is a more detailed summary of what you need to do to get it working.

Steps to go enable Widevine L1 on custom ROMs :-

• Flash OOS 11 stable. eg.11.0.5.1

• Flash Magisk then enable Zygisk + denylist.(in denylist you should select show system apps in three-dot menu,then search gms, select com.google.android.gms and .gms.unstable).

• Reboot.

• Verify if you have L1 working using app like DRM info.

• Local upgrafe OOS 11 stable (preferably same build).

• Reboot.

• Verify if you have L1 working using app like DRM info.

• Flash custom ROM and you should have L1 there as well.

If I remember correctly, you need to make sure L1 is working on OOS 11 for both partitions A and B before flashing the custom ROM, or you will probably lose L1.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Khiven:
Guys, is Android auto working properly? I can't get my car to recognize the phone with the same cable and stuff that worked on OOS12. Tried file transfer usb mode and enabled USB debugging just to try with no luck. Any idea? I'm using the full nickgapps package, tried uninstalling updates as well with no luck

Running today's build.

EDIT WORKING NOW: In case it helps someone, I uninstalled updates, installed again, cleared data and then restarted phone. It was detected right away. My guess is something was residual from previous backup by Google backup and messing the recognition.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
I got this sorted out and can answer my own question ;)

For anyone else who might be unsure about how to approach rooting with Magisk after updating: patch the boot image that corresponds to the update installed on your phone. In my case, my initial clean install was the 12/23 build, then I updated to the 12/26 build, then wanted to root my device, so I patched the 12/26 boot image and all is running smoothly with root active. I didn't try using the previous build's boot image, as everything I read in my research pointed to the importance of the patched boot image corresponding to the currently-installed OS.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] undrwater:
If you're using sideload to install Gapps, you can use it to install the latest magisk.apk. no boot patching necessary.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
Correct. In my experience, there's no need to mess around with the boot image. The steps I've used to install crDroid (or any custom ROM) on the OP7Pro are:

- Boot to recovery (assuming crDroid recovery is already installed)

- Flash/sideload crDroid

- Reboot to recovery so that the active slot switches (THIS IS IMPORTANT!)

- Flash/sideload Gapps

- Flash/sideload Magisk (*)

- (OPTIONAL) If you're running unencrypted, flash the DM-Verity/Force Decryption/YadaYadaYada script (found elsewhere)

- Reboot system

- Profit!

(*) If you're sideloading Magisk, you can keep the .apk extension on the file. If you're flashing it, though, you'll need to change the extension to .zip so that the recovery can see it.

I've never had any issues doing it this way, which is why I do a Spock eyebrow every time I read about someone going through all the convoluted steps regarding boot images and custom ROMs. (I can see that it might be necessary if you're using OOS, but I've never had to try since I put a custom ROM on every new phone I purchase; I only keep the stock ROM around long enough to unlock the bootloader.)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
Interesting! In that case, am I understanding correctly that the process would be the same for updating crDroid? i.e., sideload the latest crDroid build, reboot to recovery, then sideload Gapps and Magisk before rebooting system? And that process would retain root and all permissions settings without the need to patch the latest boot image with Magisk?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
It should, yes. I build my own fork of LineageOS with cherry picked features that I wanted for myself, and that's how I updated to new builds on my OP7Pro (and now my OP9Pro). Never lost root or permissions settings. Granted, it's a given that you'll have already installed a custom ROM and done Gapps and Magisk the first time already, the process always being a little bit different on each phone. 😉 However, updating the ROM to new releases after that should only require the steps I outlined.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] dantheobserver:
Thanks for the info and clarification! I can confirm that the process you outlined works great for updating an existing crDroid installation on OP7P. I updated my phone from the 12/26 build to the 12/30 build entirely from ADB and everything's running great with root still intact!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
You're quite welcome. The same steps should also work for other custom ROMs, as well as for going from one custom ROM to another (i.e. LineageOS to crDroid) or from one major ROM version to the next (i.e. crDroid 8.x to crDroid 9.x). In those cases, however, I

always

recommend backing up your apps and data (I recommend using Swift Backup over the outdated Titanium Backup) and doing a factory reset inside the recovery before proceeding to install the new ROM, Gapps, and Magisk (i.e. doing a clean flash). Many people have claimed that doing a dirty flash from one major version to the next hasn't caused any problems for them, but I

never

take that chance. Besides, doing a clean flash is usually a good opportunity to start with a fresh, clean slate. ;)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gap30:
dlt
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] foomo:
No ideas on this one? I still couldn't figure it out. Although at least I managed to install a working TWRP 3.7 with FBEv2 to both slots.

Also I encountered a bug with the dialer. The phone rings but no incoming calls are displayed. Installed simple dialer from F-Droid and it worked, so it seems to be a problem with the dialer shipped with crDroid.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] midgo12:
So I'm thinking of flashing crDroid latest as my new custom rom on my Oneplus7pro.

Current custom rom I am using is nearing EOL I think.

I see that there are weekly builds.

How is the rom as a daily driver pretty stable.

Any issues with video recording or playback in HD?

Any issues with low volume in playback or in general.?

Can I use the OTA function whenever there is an update.?

I will be rooting the phone so OTA is pretty handy.?

Thanks for any information guys...
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Latty:
It's stable and a great daily driver. No issues that I can speak of.

I don't use OTA as it doesn't seem to work well with Magisk (option to flash to other slot doesn't work), but ADB sideload works perfectly.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] midgo12:
Thanks for the reply.

So I have to patch the boot.img with magisk and sideload it to keep root after every update???
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] MJPollard:
If you've already rooted once, this is all you need to do if you flash an update (as opposed to using OTA):

- Boot to recovery

- Flash or sideload the ROM update

- Reboot to recovery so that the slots get switched (THIS IS IMPORTANT!)

- Flash or sideload Gapps

- Flash or sideload Magisk

- Flash or sideload anything else you need to flash

- If you're running unencrypted, flash or sideload the DM-Verity/Force Decrypt/etc. script (this step should always be last)

- Reboot to system

- PROFIT!

No need to patch boot or vendor images or anything like that if you're upgrading, and root and all your apps and data are retained.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Yochy_:
gwolf thx a lot for this rom been enjoying it a lot and have it installed on my OP7PRO. I feel like ur one of the more active developers and appreciate the hard work you put into updating crDroid and replying to fourm posts. Keep up the great work and happy new years
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] shadowikr:
It doesn't? Flashing to inactive works just fine for me
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Latty:
Maybe it's just me, but my magisk app doesn't have that option as soon as the OTA is installed..
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Toutatis_:
Which version are you using? I'm using 25.2 and after each OTA update, I just open Magisk Manager, then go to Install and choose "Install to Inactive Slot (After OTA)".
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gwolfu:
Build 20230108 is ready

Changelog: https://crdroid.net/guacamole/9#changelog

Download: https://crdroid.net/guacamole/9
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
I'm going to go the same path as you.

Have you tried MinMicroG ? That's what I'm using since CrDroid 7, and I didn't had any issue with. I'm gonna try that tonight and keep you informed :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
You fixed my issues with the Launcher!!! Thank you!!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Yochy_:
over all driver is stable. although I have issues with the occasional video playback on yt/tiktok where the vids would buffer for 8-10s before playing. was wondering if anyone has found a solutions yet?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] DrizztDWX:
I have switched today from Pixel Experience but I have problem with VoLTE and VoWIFI. I have activated them in setting but its dropping to 3G. On stock and PE it was working just fine. Is there anyway to use it here? My service provider is Orange Poland and Play Poland
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
Hello, I've installed CrDroid 9 just now, installed the latest MicroG apks and it works. Apps are detected by the GCM system.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] foomo:
Weird. I tried it several times, didnt work. But I used the microG apks from fdroid and not minMicroG. Can you post what you did step per step? Maybe I forgot something. Anyways, thanks for the reply and the suggestion of MinMicroG!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] jakegsxr11:
I'm having the no response to touchscreen issues. I thought I flashed the firmware properly but I'm guessing I didn't. Now my phone is stuck on the startup setup screen and I can't reboot it because the touch screen isn't responding. How can I reboot into recovery ADB isn't working?

Thanks
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Latty:
25.2. The option just disappears as soon as I install the OTA.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
@gwolfu : I've installed the ROM yesterday, I saw only one issue so far, when using the night screen light mode, the lockscreen stay on daylight mode

@foomo : This is what I did

Flash OOS 12 Firmware with the provided tool on the first page : https://sourceforge.net/projects/crdroid/files/guacamole/9.x/firmware/

I don't know how you're using the platform tools files to interact with adb and fastboot, but make sure the scrips can run correctly without error.

Then follow the instructions provided by the first post

Flash the provided boot.img, even if the OOS 12 Firmware script already did it

Sideload CrDroid

Reboot to system

Download the official .apk files from MicroG, you will find instructions here : https://github.com/microg/GmsCore/wiki/Installation

Follow the guide, calmly check everything, allow everything and it should work :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] jones1223:
while mobile is on adb detecting devices but once i enter cr droid recovery mode device is unauthorised how to fix that i can also side load rom and i updated latest rom v 9.0 my touch is not working any fix for that also
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
For the "unrecognized" issue it might be a driver problem. Download and install the drivers from here: https://developer.android.com/studio/run/win-usb (click where it says "ZIP file"). You may need to go to device manager in Windows and right-click the currently installed driver and select update driver. Then point to the files you just downloaded. Should be fine then. Do this while in bootloader mode on the phone.

As for the touch not working, you need to flash the OOS 12 FIRMWARE file as specified to do so in the OP you just quoted. Extract the firmware zip file and run the .bat file while the phone is in bootloader mode then follow the terminal on-screen prompts. Touch will work then.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] TapioH:
Two issues so far:

Netflix app freezes and have to force boot usually happens when pause and play

Another issues is with launcher3, when using high dpi (640) all apps gets messed up, shows a tiny strip of apps instead of full screen list

Other than this, awesome Rom!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
Try to get a log (adb logcat) when Netflix freezes then tag the dev with the file (uploaded here or pasted to something like pastebin.com). Best way to get help/get things fixed. The dev may not even have Netflix so how would he be able to help otherwise?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] jones1223:
how to flash other recovery like twrp ,while trying to flashing twrp it always reboot into cdroid recovery.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
A) This is the crDroid ROM topic, so this isn't the place to ask - there is a topic for that.

B) Pretty certain TWRP is currently not compatible with OOS 12 firmware. I tried it a few months ago and it wouldn't work - others had the same problem.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gwolfu:
Build 20230113 is ready

WARNING WARNING WARNING

!!! This update requires OOS 11.H.32 firmware !!!

Update can be done via firmware update tool linked in opening post

Changelog: https://crdroid.net/guacamole/9#changelog

Download: https://crdroid.net/guacamole/9
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] lightchess:
Hi. Videos from some social network apps can not be played. This issue can be constantly reproduced with VK app, just install and search for videos, attached screenshot. When I open link for that video in mobile Chrome or Bromite browser, no such issue.

Is it possible to fix? Issue doesn't occur with other ROMs.