yashsingh1/xdaforums huggingface dataset:
[OnePlus 11] kdrv3xc:
Sounds like you somehow ended not changing your active slot after the update. (e,g you were on slot a before the update, and still rebooted to slot a instead of slot b). always make sure you reboot after update before flashing anything. after update you should always get crdroid recovery first. if you're already on crdroid, i wouldn't bother doing a factory reset unless nothing else is working. if you can get to recovery just sideload again, if it gives you that partitions error again switch slots with

fastboot --set-active=other

and try again. If that fails you can still do the update-firmware script, but that till shouldn't require a factory reset.

after sideloading the rom though, rebooting to recovery should always land you in crdroid recovery. recovery is an OTA partition.

so more like this:

When next update becomes available

:

Reboot to TWRP recovery

Make a full backup and save it outside of the device

Sideload ROM

Reboot to TWRP recovery (crdroid recovery)

Sideload GApps & magisk if you want that

Reboot to System, check everything is well

now reflash twrp

The most important takeaway here is after an update, regardless of the method, rebooting to recovery should always land you crdroid recovery. this also has the added benefit of telling you which build your on to confirm it was successful.
[OnePlus 11] kdrv3xc:
no just reboot to bootloader and flash this before updating to the 0830 or later build

crDroid Android - Browse /salami/9.x/firmware at SourceForge.net

Highly customizable Android Platform

sourceforge.net

it'll drop you in recovery, where you can either sideload the update or reboot to system to update via the built in updater if you're already on crdroid.
[OnePlus 11] kdrv3xc:
more of just a hobby project for me. the only device ive tried it on is an old samsung galaxy tab e, and everything about that isn't very appealing to me.
[OnePlus 11] m0han:
New TWRP, crDroid Recovery, crDroid ROM etc. available. So, I guess I'll first update TWRP recovery and then follow the rest of the procedure above. Or, should I first try through 'local update', since it worked (for you), albeit on the second try?
[OnePlus 11] Ćwirek:
Done. Now - root. Result of the method with sideloading Magisk.apk file was that UI crashed and Internet (mobile and WiFi) didn't work. When I get rid of the Magisk app everything is normal again. How can I get root?
[OnePlus 11] jeffsga88:
Did you sideload Magisk right after installing Rom or did you boot into system first and then reboot to recovery and sideload Magisk? If you did the first way right after installing or updating that's most likely the issue, if you did the 2nd way not sure. I installed Rom, rebooted into system, then after setting up phone, rebooted into recovery and sideloaded Magisk. When you boot back up and open Magisk it will say additional setup required, hit cancel and then click on install and choose direct install and then reboot. Also I use Magisk Delta, although I would assume stable or canary would work just as well.
[OnePlus 11] kdrv3xc:
adb sideload magisk.zip/magisk.apk

reboot

open magisk app and it will make itself install itself again just hit ok and reboot it will reboot again
[OnePlus 11] kdrv3xc:
if possible id always prefer the live update, but all in all it shouldn't make too much of a difference. just be sure to reboot to recovery right after installing the zip and make sure you're in crdroid recovery, then sideload gapps and magisk. reflash twrp as the absolute last step (after rebooting to system and opening the magisk app which will need to install itself the right way)
[OnePlus 11] m0han:
Since I'm running TWRP recovery now, does this above have to be done

prior to

attempting the live (local)

update as well

? (I mean fastboot flash recovery_a recovery-20230911.img and fastboot flash recovery_b recovery-20230911.img.) I already have the files (crDroid Recovery and ROM) downloaded and transferred to the phone.
[OnePlus 11] kdrv3xc:
no, just after however you choose to install the update, always reboot to recovery. when rebooting to recovery after installing an update you should always be in crdroid recovery. if you're in crdroid recovery after installing an update then that's perfect. once you've rebooted into crdroid recovery immediately following installing the update, flash gapps and magisk. then reboot to system. open magisk at this point, magisk will say it needs to be installed again from the app. if it doesn't automatically do that for you then hit install > direct install. then reboot again. after this you can reboot to bootloader and flash twrp.

so to recap:

install the update

reboot to recovery regardless if you're already in recovery or anything else. this is important.

make sure you followed step 2

if you followed steps 2 and 3 you will now be in crdroid recovery with it displaying the build date of the update you just installed

flash gapps and magisk (from crdroid recovery)

reboot to system

open magisk app, direct install method

reboot to system again

now feel free to reboot to bootloader now and flash twrp
[OnePlus 11] Ćwirek:
Boot into system, boot into recovery and sideload Magisk.apk and nothing happened.

As above.

Maybe I need to clean install ROM?
[OnePlus 11] m0han:
Started with TWRP installed. Got stuck for more than 20 min at finalising package installation (as before) and had to cancel the installation.

Rebooted to bootloader and flashed crDroid Recovery of 10-Sept. Rebooted to System to try 'local update' again. This time it completed in less than 30 min. Rebooted to crDroid Recovery (of 11-Sept ROM). Flashed GApps and rebooted to System.

Not sure if switching to crDroid Recovery was what ensured completion of the update. Didn't have the patience to wait longer on the attempt with TWRP installed.

I think it'd be better this way: Install TWRP & get backups, then flash crDroid Recovery and use that to sideload ROM and GApps. Might be easier to get the job done; at least until TWRP gets equipped to install ROM updates without issues.
[OnePlus 11] kdrv3xc:
yeah by this point if you don't have a backup. always flash gapps before rebooting to system, but reboot to recovery first. see my above post. do not boot into system after update before booting back into recovery and flashing gapps.

for now i'd stick with just installing whatever updates they officially put here or push via OTA. if you're on a 9/10 build there's no reason to go through all this to update to a build 1 day later that has no changelog or anything. if there's this many builds this frequently they're most likely debugging/troubleshooting something and that's likely to cause more trouble than it's worth.
[OnePlus 11] m0han:
I agree with you. The reason I went for it was to test if it'd work for me. I hadn't done a local update of crDroid before.

> Not sure if switching to crDroid Recovery was what ensured completion of the update. What do you think? I ask 'cos you're a 'Recovery Builder' yourself.
[OnePlus 11] kdrv3xc:
oh i wouldn't go as far that, i'm still just figuring it out...but i am making progress. without seeing logs/more information i can't say for sure either way. i don't think it should make much of a difference, but if it were to make a difference i'd say it's more likely to work on its native recovery than a custom if it comes down to it. i mean technically this twrp is built for android 12, and this is 13, they're supposed to be compatible, and i haven't run into any issues, but there could just be one line of code that breaks thats compatibility. that's why backups are important. i'm actually checking out this magisk module that supposedly can create a /data backup live, so you wouldn't have to boot to twrp to make the backup, and can be restored via magisk or twrp...that would be cool if it works, i'll update later on that.

i think the last update just took longer to install than normal. i tend to be pretty impatient, and i probably should have waited a bit before i just said it was stuck. i really had no other reason to think that and i should have at least looked for something to confirm there actually was an issue. i should have grabbed the logs. next update i'll do that just to satisfy my own curiosity.
[OnePlus 11] Ćwirek:
Everything went fine when done clean instalation, so maybe next time I just skin the update part and just do clean install instead
[OnePlus 11] karliyo:
What to do if after running update-firmware.sh it rebooted to recovery but device was now unauthorized for adb?

❯ adb sideload crDroidAndroid-13.0-20230910-salami-v9.8.zip

adb: sideload connection failed: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

❯ adb devices

* daemon not running; starting now at tcp:5037

* daemon started successfully

List of devices attached

4fbcf775 unauthorized

After rebooting and getting back into recovery, I "enabled" adb from advanced menu and now it's showing up as "recovery" device but sideload fails.

❯ adb devices

List of devices attached

4fbcf775 recovery

❯ adb sideload crDroidAndroid-13.0-20230910-salami-v9.8.zip

adb: sideload connection failed: closed

❯ adb kill-server

❯ adb sideload crDroidAndroid-13.0-20230910-salami-v9.8.zip

* daemon not running; starting now at tcp:5037

* daemon started successfully

adb: sideload connection failed: closed

EDIT: Easy fix, but could use a documentation update. You need to go to `Apply update` -> `Adb sideload` before running `adb sideload ....zip`

After successful installation of gapps+rom, I'm getting some fatal exceptions. It's still working but these apps/services consistently crash.

1) Android System Intelligence crashlog: https://paste.crdroid.net/aBLQfN

I didn't find a way to add this permission but I didn't bother searching about it yet. This exception comes right after restarting. "Android System Intelligence keeps stopping"

2) Settings crashlog. Also comes after restart. https://paste.crdroid.net/2jEuUP
[OnePlus 11] m0han:
Not sure if you formatted data before sideloading the ROM zip. If you follow the instructions in the OP to the letter, you should be fine.

..... run Update-firmware.bat (windows) or Update-firmware.sh (linux) It will auto-reboot in recovery after completion.

While in recovery mode, factory reset (wipe/format data) and sideload the installation .zip

adb sideload <crdroid zip>

It will complete at 47%.

IMPORTANT: To flash additional packages like Gapps, reboot to recovery (right) after ROM installation/update....

Reboot and enjoy
[OnePlus 11] kdrv3xc:
you don't need to enable adb in advanced to sideload anything. you just need to go to apply update.

adb devices will show:

List of devices attached

4fbcf775 sideload

enabling abd shows:

List of devices attached

4fbcf775 recovery

which is a completely different protocol that you cannot sideload from.

a nice addition they made is after sideloading the rom it tells you to reboot to recovery again to sideload gapps/magisk. if you don't reboot again you're going to be flashing to the soon to be inactive slot resulting in the above errors.
[OnePlus 11] karliyo:
Yep I forgot to initially format data and had to flash the ROM again.

The other exceptions are still valid and I'm still seeing them occasionally.
[OnePlus 11] m0han:
I wasn't aware of the difference between the two protocols and had always enabled ADB and only then applied update via sideload. But, it has worked for me all the time.
[OnePlus 11] kdrv3xc:
hitting apply update restarts adbd in sideload mode. enable adb and adb shell then hit apply update and apply update from adb (putting it in sideload mode) and you'll notice your shell disconnects.

there's no harm in doing it but you're essentially just flicking a switch
[OnePlus 11] ebukelepce:
kullandığımm en iyi rom teşekkürler
[OnePlus 11] DragoWing:
Does this rom support esim? i cant seem to get it to work, :O
[OnePlus 11] m0han:
This question seems to have been answered before. Please search. As for hardware support, OnePlus 11 phones sold in North America supports eSIM and dual SIM cards.
[OnePlus 11] DragoWing:
** edit **

oops, sorry it went through twice, sorry
[OnePlus 11] DragoWing:
i know, i wouldn't have asked if i found it, on google and xda, can u maybe provide a link? I have an esim supported phone, Europe, but when i flash this rom it won't find esim, only on my stock rom it seems to work...
[OnePlus 11] m0han:
If you're keen to stay on crDroid, you could wait for eSIM-OP11 users or the ROM dev to comment. If not, maybe this post (found here on xda) could help you move on. https://xdaforums.com/t/rom-13-op11-crdroid-v9-8-official-10-sep-23.4610649/post-88924623
[OnePlus 11] DragoWing:
Ah, thank you so much for your help, ill think ill go back to stock rom or try out nameless instead till the esim functionality is fixed, thank you for your help, <3
[OnePlus 11] karliyo:
Do you guys have a passing SafetyNet?

I have Magisk 26.3 installed via recovery + renamed app + denylist for Google apps + Zygote, however YASNAC says CTS profile and basic integrity are "Fail" and thus Google Pay doesn't work either.

On my old OP9Pro I have AOSP 13 + Magisk 25.2 with same settings and safety net is passing fine.
[OnePlus 11] neobuddy89:
crdroid.zip is example

Use actual file name.
[OnePlus 11] taaviu:
PS C:\Users\Taaviu\Desktop\OP11\cDroid> adb version

Android Debug Bridge version 1.0.32

PS C:\Users\Taaviu\Desktop\OP11\cDroid> adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

f2582exx sideload

PS C:\Users\Taaviu\Desktop\OP11\cDroid> adb sideload crDroidAndroid-13.0-20230729-salami-v9.7.zip

loading: 'crDroidAndroid-13.0-20230729-salami-v9.7.zip'

* cannot read 'crDroidAndroid-13.0-20230729-salami-v9.7.zip' *

PS C:\Users\Taaviu\Desktop\OP11\cDroid>

Will try with another PC...
[OnePlus 11] ChrisFeiveel84:
And try it with cmd and not with powershell
[OnePlus 11] taaviu:
Been there with cmd, cmd admin, powershell. Now copying files and will give a try with another PC

With Lineage same thing...but Lineage recovery working good.

"

C:\Users\Taaviu>adb sideload uptade.zip

loading: 'uptade.zip'

* cannot read 'uptade.zip' *

C:\Users\Taaviu>" with CMD same thing, its pc problem. will look closer after phone will boot.

EDIT: problem with my main PC, laptop sideloading fine.....will wait to first boot.
[OnePlus 11] ChrisFeiveel84:
In your screenshot you use the Powerahell and not the cmd

And use the last android platfrom tools
[OnePlus 11] SparkyKitty:
It appears to be the boot.img that is causing it to hang on the oneplus logo, flashing the lineage boot appears to have fixed it.
[OnePlus 11] taaviu:
Finally got it setup. Some weird thing with my main PC, laptop helped out. First impression is holy f**k how good can be clean Android. Will investigate further. Thanks everybody who will did this rom available and helped.

EDIT: used lineage recovery, boot and vendor
[OnePlus 11] Daniel_Leung:
me too please help me
[OnePlus 11] taaviu:
Pm or write here. But i downloaded Lineage boot.img, venorxx.img, recovery.img and flashed those. Then sideloaded .zip
[OnePlus 11] Aleplus:
And how then, for example, to return to Oxygen OS?
[OnePlus 11] Daniel_Leung:
Thanks, already entered crDroid fastboot and adb sideload crDroidAndroid-13.0-20230729-salami-v9.7.zip

serving: 'crDroidAndroid-13.0-20230729-salami-v9.7.zip' (~14%)
[OnePlus 11] taaviu:
Only with DownoadTool...tested, (yes there is another option too, but it is pretty bulletproof and bumbproof.
[OnePlus 11] Daniel_Leung:
adb sideload crDroidAndroid-13.0-20230729-salami-v9.7.zip done,But the restart failed, the mobile phone black screen did not respond
[OnePlus 11] Matei Mihai:
Hello, I can't sideload crdroid, even though sideloading lineage and Gapps works completely fine...I tried CMD, PowerShell, both lineage and Crdroid recoveries...
[OnePlus 11] miguelito18:
fingerprint not working
[OnePlus 11] neobuddy89:
OP updated for

crdroid-installation.zip => lineage-installation.zip for now.
[OnePlus 11] ChrisFeiveel84:
Nope and with fastboot and fastbootd
[OnePlus 11] omariscal1019:
anybody get esim to work
[OnePlus 11] KechDroid:
Thank you to all the developers here, I just have a small question, my bootloader is already unlocked and I am rooted on CPH2449_11_A08, do I flash the rom directly or should I upgrade OxygenOS?
[OnePlus 11] ChrisFeiveel84:
I thing the rom used blobs from oos 13.1.0.580 better you Updater First to oos 13.1.0.580 build and flash than the rom
[OnePlus 11] kdrv3xc:
GitHub - Displax/safetynet-fix: SafetyNet & Play Integrity API workarounds for Magisk

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[OnePlus 11] WorldTeacher:
Hello,

i have a small problem. I had to re-install crDroid because I couldn't update to newer versions. The re-install went fine, but now I have a charging issue. Every charger I use will, at max supply 4V 1100mA (mostly somewhere around 500-800mA), while the original charger ramps up to 4V 5000mA. Before, all chargers supplied at least 5V 2000 mA. I have tried using the XCharge magisk module to increase the charge value, as well as another module, both did not fix the problem. I've noticed that in Settings>OnePlus Settings> USB has Fast Charge enabled (decription says: "Force fast charging of up to 900mA in USB 2.0 mode") and is greyed out, so that I can not disable it.

is it like that for everyone else using crDroid 9.8 build date 10.09.2023?

If not, is there anything I can do to speed up my charging, even If I'm not using the original charger?

Any answer is appreciated, thanks in advance.
[OnePlus 11] NatureCat:
Hey, Did anyone have any luck so far using MicroG instead of the "official" GApps?

I already tried multiple things, but none of them have worked so far...

Using Magisk+Zygisk and LSPosed, if that helps.
[OnePlus 11] Ćwirek:
A question for everyone who is not satisfied with the battery life - did this problem appear only after installing some Magisk modules, such as AOSP Mods in the full version (Magisk + Zygisk), or is the relatively short battery life irrelevant depending on the installed modules?

I'm asking because I switched to LineageOS and the battery life was quite promising, but after installing the Magisk modules it changed significantly.

The problem is that I installed the modules one after another (with restarts after flashing) and now I don't really know what could cause a possible problem, and only AOSP Mods were able to boot phone into recovery where there was information that the software was probably damaged, but after selecting the restart option, the phone turned on and works normally.

I'm writing about it here only because I know that the topic of batteries has been discussed here.

Any ideas?
[OnePlus 11] karliyo:
Wonderful, thanks. YASNAC now shows all as passing.
[OnePlus 11] sergjhb:
Wrong!

I dealing with the solar batt business professionally. Li batteries is NOT the Lead batt and all that myths comes from stone age of th Lead batt!
[OnePlus 11] dekefake:
Multiple studies show lithium batteries degrade faster the more we charge them close to 100%.
[OnePlus 11] sergjhb:
Fake.

I am physicyst/power electronic designer and know nearly all about this issue.

One more time - fake
[OnePlus 11] kdrv3xc:
people who say they know "nearly all there is to know" about something tend to know very little. it's an interesting phenomenon...

https://pubs.acs.org/doi/10.1021/acsaem.2c02047

what stuff do you design/build? i'd like to avoid it.
[OnePlus 11] sergjhb:
Don't make conclusion if you see word Lithium - there is plenty different types of Li batteries with different properties.

Your link point to different type -

We have investigated the effects of state-of-charge (SoC) and temperature on the degradation of commercial lithium-ion batteries with Si–Gr/NMC811 electrodes.

In our phone used different type of Li batt with different characteristics.

Also discharging currents are low - around 0.1C

My previous phone 7T PRO for now 3.5 y old. Battery sitting on 95% capacity. I was recharging it every possible moment - it was most of the time 80 - 100% full.

And BTW - i involved with Solar systems design and had to learn a lot about different Li-Ion batteries and they properties.
[OnePlus 11] DHD22800:
Hi guys.

I've noticed some little things:

1) connected my Jabra Elite 75t and I haven't audio on bluetooth. Tried to disable high quality in Bluetooth settings (was default enabled) and now works...maybe a bug?

2) can't login by clicking yes on this devices...previously, on OOS, I could login on Google by clicking yes on my device, now I can't... (Gapps linked in 1st post)

3) the battery drains faster compared to stock OOS, managed to blocked sensors in crDroid to Instagram, reddit etc.

4) when enabling taskbar in launcher settings, it is on top of navbar

Is there a solution for the 2nd point?

Thank you

EDIT:

I have just solved the 2nd point, just deleted play store service and Google cache and data. Now works lol
[OnePlus 11] Dinw:
I can't get Jabra Elite Active 75t earbuds to work for media though they work just fine for calls. Firmware is 2.0.0 the latest. I've tried with two different pairs.

I've tried disabling HD audio, but it makes no difference.

This is on 9.8 from September 10th rooted with Magisk.

Does anyone have any advice on how I can get them to work?

Thanks.
[OnePlus 11] DHD22800:
I simply connected with Bluetooth, play Spotify and no audio from headphones. So I was gone in Bluetooth options and disabled hd audio, then I could play Spotify....

Try to change Bluetooth codec in developer settings. Maybe it will fix
[OnePlus 11] Dinw:
I had tried that already, but now I did it while they were connected and it worked. Fantastic. Thank you.
[OnePlus 11] neobuddy89:
New Update Available

===== 26 September, 2023 =====

- Android September 2023 Security Update

- Improved double-tap-to-sleep implementation, now works even on doze screen

- Fixes and updates for keyboard and calendar apps

- Crash fixes for Dialer app

- Fixed screen-off UDFPS / FOD not working correctly

- salami: Switched to source-built DTBO

- salami: Added OnePlus settings for game mode and edge touch

- salami: Updated haptics implementation

For download link, telegram discussion link, refer to the first post.
[OnePlus 11] karliyo:
I thought I was the only one with this unusual BT audio problem. Bose QC35 works perfectly out of box but Jabra Elite Active 65T has no sound. Both work perfectly on OP9Pro with AOSP rom.

Disabling HD audio also worked for me, thanks.

Both devices had the same options while OP11 had no audio and OP9Pro had.
[OnePlus 11] DHD22800:
I've Bose QuietComfort Earburs and Sennheiser Momentum 4. Didn't checked if they works.

I think (and Hope) that the developer Will fix!

But at the end audio works so isn't a "main" bug.
[OnePlus 11] m0han:
Seeing several posts about issues with this 'official' build (the first after 10-Sept) on Telegram and other forum threads for OP11.
[OnePlus 11] kherio:
What is the correct way to update it via OTA? The last update i lost everything.

Once the OTA is installed, before rebooting magisk on the other slot and reboot in recovery for reinstall gapps? Or what is the recommended way?

thx in advance
[OnePlus 11] sergjhb:
Tryed today 2 times with ROM dowloaded from official side and mirror - both not installed for me

ERROR: Payload.bin Size Miamatch

Went back to 24th Sep
[OnePlus 11] DHD22800:
The correct way *should be*:

1) flash latest recovery if available (not mandatory even if expressed by dev)

2) sideload ROM,

3) reboot to recovery ,

4) flash gapps

5 -optional) magisk.

For me was the same:

I have tried 2 times and both with error kPayloadSizeMismatchError.

I tried both latest recovery and recovery from firmware.zip
[OnePlus 11] m0han:
Hope the dev provides advice with either (i) proper steps for using the same build if there is nothing wrong with it or (ii) indicating the correct earlier build that would work well so users are spared some agony.