Development [ROM][13][OOS Cam][OP9] crDroid v9.2 [12.03.2023]

Search This thread

Fireblast3

Senior Member
Feb 13, 2017
71
10
OnePlus 5T
Xiaomi Redmi Note 7

gecko8k

Senior Member
Apr 6, 2016
167
36
Updated it boot up fine, but forgot to sideload gapps and app keep crashing, so I went to sideload them and then it went to a boot loop. Since then I am not able to boot I tried to install the rom again, reboot to recovery and sideload gapps to no success.
I know it's not the solution you hoped for but you can always use MSM Tool to completely reset your phone back to stock. I wrote a short guide about it.
 

Fireblast3

Senior Member
Feb 13, 2017
71
10
OnePlus 5T
Xiaomi Redmi Note 7
I know it's not the solution you hoped for but you can always use MSM Tool to completely reset your phone back to stock. I wrote a short guide about it.
Thanks for trying to help I do know how to use MSM tool, I just dint want to go through the hassle of setting up the device.

Edit: In the end I ended up formatting in recovery. I am now setting up.
 
Last edited:

gecko8k

Senior Member
Apr 6, 2016
167
36
Hi gwolfu

Thanks for the new build. I tried it out and it's great. As far as I can tell you fixed the very bright auto brightness which is really cool. Hm, the auto brightness still seems too bright, I am hoping it gets fixed. And thanks for putting the big play button on quick settings media player a while ago.

I noticed a couple of things that you might have overlooked or could have interest in looking into.

Bugs (I think):
  • The lock screen shortcuts seems buggy. Only flashlight and camera seems to work, while e.g. wallet and QR scanner are turned into either flashlight or camera at the lock screen. If it could also be possible to start any app it would be cool.
  • Battery estimates in quick settings does not seem to work, it just displays battery percents when estimates is toggled on.
  • Maybe it is a hardware fault on my phone but the top speaker seems to have very low volume. Anyone else experiencing this? Edit: I tried flashing Project Extended and the speakers work just fine there so I figure it is a software issue.
Suggestions:
  • Add song duration in quick settings media player.
  • Make it possible to like a track in quick settings media player if the music service supports it.
  • Add LED notifications so the LED can tell the battery state and which app has given you a notification. Nevermind, I found out that the OP9 does not have a LED 😄.
  • Screen calibration like night light, white balance and colour calibration does not work at the lock screen or when apps ask for finger print authentication. Instead the screen is uncalibrated these places. Is it possible to make the calibration work there?
 
Last edited:

wizardknight

Senior Member
Nov 1, 2009
1,093
312
Seattle WA
Hello I am trying to install crDroid on my OnePlus 9 (LE2115).
I started with stock firmware F18. I executed the dtbo, vendor, and boot image flashes without any errors. Then I tried to reboot into recovery. The phone sat on the 1+ / unlocked orange warrning screen for a long time. Then it finaly showed the Qualcom CrashDump Mode screen. So I guess I am going to have to MSM the phone. Can anyone give me an idea what I might be doing wrong? I can't get to the point where I can sideload the crdroid.zip.

Update:
Got it figured out. I had to update the stock firmware to F17 via OTA, and then use the F18 updater from the CRdroid page. Then I had to format the system. There was no need to flash dtbo, vendor, or the boot image when done that way. The script took care of those things.
 
Last edited:
  • Like
Reactions: gecko8k

wizardknight

Senior Member
Nov 1, 2009
1,093
312
Seattle WA
Just curious, but does anyone know if we can remove the orange state boot screen while running this rom? It seems that it can be removed from stock as described here:
and noted here:
 
Last edited:

zompimalakae

New member
Jun 30, 2016
1
1
I haven't had any issues removing the orange state as described in those links, and have removed it for the last couple updates without any problems.

You'll need to repeat the steps when you update your rom, but it can be done with terminal emulator/termux if you have root.

I've been using the "abl.img" extracted from the last crdroid image before F18 firmware started being required. I'm attaching the file to this reply but you can also just use "payload dumper" to get it yourself if you'd like.
Just curious, but does anyone know if we can remove the orange state boot screen while running this rom? It seems that it can be removed from stock as described here:
and noted here:
 

Attachments

  • abl.img
    204 KB · Views: 5
  • Like
Reactions: wizardknight

wizardknight

Senior Member
Nov 1, 2009
1,093
312
Seattle WA
I haven't had any issues removing the orange state as described in those links, and have removed it for the last couple updates without any problems.

You'll need to repeat the steps when you update your rom, but it can be done with terminal emulator/termux if you have root.

I've been using the "abl.img" extracted from the last crdroid image before F18 firmware started being required. I'm attaching the file to this reply but you can also just use "payload dumper" to get it yourself if you'd like.
Thanks.
It worked perfectly for me.

Just in case anyone else wants to do this too... I used method #1 as described here https://www.droidwin.com/how-to-remove-orange-state-warning-on-oneplus-android-13/
with the file @zompimalakae provided above.

Here's my command prompt lines. There are a couple extra steps where I cd'ed to /sdcard to make sure the files were where they were suppose to be. You might need to make some small adjustments if depending on if your A or B slot is active.

Code:
c:\platform-tools>adb shell
OnePlus9:/ $ su
OnePlus9:/ #

OnePlus9:/ # getprop ro.boot.slot_suffix
_b

OnePlus9:/dev/block # dd if=/dev/block/by-name/abl_b of=/sdcard/abl.img.bak
16384+0 records in
16384+0 records out
8388608 bytes (8.0 M) copied, 2.786876 s, 2.8 M/s

OnePlus9:/dev/block # blockdev --setrw /dev/block/by-name/abl_b

OnePlus9:/dev/block # cd /sdcard
OnePlus9:/sdcard # ls
Alarms   Audiobooks  Documents  Movies  Notifications  Pictures  Recordings  SwiftBackup  abl.img.bak
Android  DCIM        Download   Music   Photos         Podcasts  Ringtones   abl.img


OnePlus9:/sdcard # dd if=/sdcard/abl.img of=/dev/block/by-name/abl_b
408+0 records in
408+0 records out
208896 bytes (204 K) copied, 0.016695 s, 12 M/s
OnePlus9:/sdcard # exit
OnePlus9:/dev/block #
c:\platform-tools>
 
Last edited:
  • Like
Reactions: zompimalakae

wizardknight

Senior Member
Nov 1, 2009
1,093
312
Seattle WA
@gwolfu
I am unable to get my phone to connect to my car's Bluetooth. It starts the process like normal. Then as soon as I enter the pin, it connects and immediately disconnects. If I try to reconnect it connects for a second then disconnects again. Bluetooth works as expected on the latest stock rom and the Nameless rom.

I am on the 20230211 build.
I am wondering if it might be related to the Bluetooth issues being reported with the Pixel Jan security update in this reddit thread.

At the end of that thread it was being reported that the Feb update seems to resolve the issue.

I was curious if this rom might be pulling from the Jan security update code they are referring to.
 
Last edited:

gwolfu

Recognized Developer
@gwolfu
I am unable to get my phone to connect to my car's Bluetooth. It starts the process like normal. Then as soon as I enter the pin, it connects and immediately disconnects. If I try to reconnect it connects for a second then disconnects again. Bluetooth works as expected on the latest stock rom and the Nameless rom.

I am on the 20230211 build.
I am wondering if it might be related to the Bluetooth issues being reported with the Pixel Jan security update in this reddit thread.

At the end of that thread it was being reported that the Feb update seems to resolve the issue.

I was curious if this rom might be pulling from the Jan security update code they are referring to.
will try some changes with next update
logcat would help however
 

Top Liked Posts