[ROM][Android 12][CHIME - POCO M3 / Redmi 9T / Redmi 9 Power / Redmi Note 9 4G] crDroid v9.0 [OFFICIAL][28.12.2022]

Search This thread

Abhi_T

Senior Member
Apr 2, 2019
72
12
Hi, I currently have stock MIUI 12.5X. should I first install the old crDroid v7 juice version and after that the v8 chime version ? If no, how should I proceed please ? Is there a guide ? I checked the github but didn't find any guide. Thanks in advance.
What is your device (poco m3, redmi 9 power or redmi 9T) ?
 

Grudger

Member
Oct 26, 2012
34
3
Karachi
Can I update from 8.6 to 8.9 ?

8.9 is here:

Changelog:
- Updated security patch level to 2022-09-05
- PixelPropsUtils: Update fingerprints to September 2022 release
- Switched to Anya kernel
- Added ability to resize QS & Statusbar Clock
- Dialer: Added toggle for post call snackbar
- Dialer: Move Sensor settings to Other settings
- Update statusbar burn-in protection shift base padding when orientation changed
- Added smart charging
- Added reset battery stats option
- Update Chromium Webview to 105.0.5195.68
- Some small dark mode fixes
- Updated translations
 

mp44christos

Member
Aug 9, 2013
28
4
POCO M3
I tried to update from 8.8 to 8.9 and go stuck in the bootscreen. I managed to install 8.9 using abhi steps (flashing no oss vendor before the rom).

For future reference can anyone provide me with which steps to go about installing the update?

Poco M3 twrp 3.6.2
 
  • Like
Reactions: Grudger

sgt-baker

New member
May 10, 2016
4
1
Hi, how to make this rom work with Redmi 9T lemon? This is version with NFC, i know that for crDroid with android 11 i had to install custom kernel for screen to work
 

mp44christos

Member
Aug 9, 2013
28
4
POCO M3
New update 8.10 came out. If someone knows how to successfully apply this update over the current install, plz tell us the exact steps and recovery used.
 
Last edited:

imayoda81

Senior Member
Apr 27, 2006
472
180
I need help guys..

I have flashed 8.10 version over a 8.5, not reading the thread ... it blasted my data, system and rendered the thing a black screen after another..

I only succeeded in reinstalling latest MIUI, but now for me it is impossible to flash a new recovery and start over again.
Everytime I flash a recovery in can't boot (black screen), only the MIUI one can.
Tried orangefox, twrp and old pitchblack ... nothing.
I'm a little desperate now :( and looking for kind suggestions, please.
Thank you all in advance
 

redair70

New member
Nov 4, 2022
2
0
For each new installation, I proceed as follows:
with TWRP
Data format
Wipe Data, Cache and dalvik
reboot in recovery
flash Miui_CITRUSEEEAGlobal_V12.5.7.0.RJFEUXM_5435a06274_11.0
then directly flash the new rom
wipe dalvik/cache
reboot system
 

imayoda81

Senior Member
Apr 27, 2006
472
180
I need help guys..

I have flashed 8.10 version over a 8.5, not reading the thread ... it blasted my data, system and rendered the thing a black screen after another..

I only succeeded in reinstalling latest MIUI, but now for me it is impossible to flash a new recovery and start over again.
Everytime I flash a recovery in can't boot (black screen), only the MIUI one can.
Tried orangefox, twrp and old pitchblack ... nothing.
I'm a little desperate now :( and looking for kind suggestions, please.
Thank you all in advance
understood what's the problem

My device (truly v2 panel) is NOT supported by newer recovery.. not even one, tried twrp 3.6.2 and orangefox mod by fgrkprjkt ...
So that means that I can't get any newer rom anymore on my poco m3.
very sad :(
 

noogi

Senior Member
Dec 13, 2016
151
30
Gdańsk
Moto E5
understood what's the problem

My device (truly v2 panel) is NOT supported by newer recovery.. not even one, tried twrp 3.6.2 and orangefox mod by fgrkprjkt ...
So that means that I can't get any newer rom anymore on my poco m3.
very sad :(
Try this TWRP: https://github.com/sergeantkakashi/Action-Recovery-builder/releases/download/3356097348/recovery.img
or OrangeFox:
https://drive.google.com/uc?id=1c_fuMzNN1NLXh2CS43BeAsbgsgWXb9b7&export=download

all credits to: https://tgstat.com/channel/@Redmi9TUpdates
 
  • Love
Reactions: imayoda81

imayoda81

Senior Member
Apr 27, 2006
472
180
@noogi bad luck :( :(

tried both recoveries and only twrp works (orangefox goes to blank screen forever), but after flashing all packages (rom + nickgapps + magisk) it only reboots to a forever black screen with no backlight nor image..
tried even some known to work (from near past) kernels, but nothing...only a blank screen
 

noogi

Senior Member
Dec 13, 2016
151
30
Gdańsk
Moto E5
@noogi bad luck :( :(

tried both recoveries and only twrp works (orangefox goes to blank screen forever), but after flashing all packages (rom + nickgapps + magisk) it only reboots to a forever black screen with no backlight nor image..
tried even some known to work (from near past) kernels, but nothing...only a blank screen
At least one recovery is working ;) Try other roms from link above.
 
  • Like
Reactions: imayoda81

imayoda81

Senior Member
Apr 27, 2006
472
180
tried other roms, same situation, after boot it suddenly becomes black screen.. strange that this happens every time with every rom i've tried o_O
 

solar10

Member
Migrated my Poco M3 to crDroid/Android 12.1 yesterday and I am getting notification already for an update.
Question: Where does this update get downloaded? My phone restarts in recovery but I can't find the file to install update. What is the absolute path to the folder where updates are downloaded ?
 

mastawindu

Senior Member
Sep 4, 2009
312
114
Hi guys,
I am a long time rom flasher. My wife has a Poco M3 (citrus?) and would like to flash it with CrDroid since she's experiencing some lags with MIUI (12.5.8.0 RJFEUXM UI).
I have looked everywhere for hours and still can't figure out answers to these questions, can you please help me ?
- Can I flash CrDroid Android 11 over her curent stock version ? (I just want something very stable and reliable)
- Any link for a working recovery ? (can't find that for sure)
- Do I need to flash anything else like vmbeta, verity no encrypt... ?
- Any comprehensive first flash guide even from another thread ?

I want to avoid any bootloops. I have already unlocked the BL via MiUnlock.

Thank you very much for you time
 

WJeffrey

Member
Dec 19, 2022
6
0
POCO M3
Hey @GtrCraft
I built Lineageos using your trees and I'm getting weird errors regarding Bluetooth

12-24 18:34:05.731 3254 3861 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 3861 (HwBinder:3254_1), pid 3254 (droid.bluetooth)
12-24 18:34:06.057 1309 1644 W WindowManager: App freeze timeout expired.
12-24 18:34:06.186 3931 3931 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-24 18:34:06.186 3931 3931 F DEBUG : Build fingerprint: 'POCO/citrus_global/citrus:11/RKQ1.201004.002/V12.5.8.0.RJFMIXM:user/release-keys'
12-24 18:34:06.186 3931 3931 F DEBUG : Revision: '0'
12-24 18:34:06.186 3931 3931 F DEBUG : ABI: 'arm64'
12-24 18:34:06.186 3931 3931 F DEBUG : Timestamp: 2022-12-24 17:34:05.811952750+0000
12-24 18:34:06.186 3931 3931 F DEBUG : Process uptime: 0s
12-24 18:34:06.186 3931 3931 F DEBUG : Cmdline: com.android.bluetooth
12-24 18:34:06.186 3931 3931 F DEBUG : pid: 3254, tid: 3861, name: HwBinder:3254_1 >>> com.android.bluetooth <<<
12-24 18:34:06.186 3931 3931 F DEBUG : uid: 1002
12-24 18:34:06.186 3931 3931 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
12-24 18:34:06.186 3931 3931 F DEBUG : Abort message: '[1224/173405.712382:FATAL:hci_layer.cc(487)] hci_root_inflamed_abort: error_code = 0, vendor_error_code = 179
12-24 18:34:06.186 3931 3931 F DEBUG : #00 0x000000722333ef47 /system/lib64/libchrome.so+0x00000000000bbf47
12-24 18:34:06.186 3931 3931 F DEBUG : #01 0x000000721fc2fddb /system/lib64/libbluetooth.so+0x0000000000300ddb
12-24 18:34:06.186 3931 3931 F DEBUG : #02 0x000000754478a263 /system/lib64/libhidlbase.so+0x0000000000056263
12-24 18:34:06.186 3931 3931 F DEBUG : #03 0x00000075447abcff /system/lib64/libhidlbase.so+0x0000000000077cff
12-24 18:34:06.186 3931 3931 F DEBUG : #04 0x00000075447abbff /system/lib64/libhidlbase.so+0x0000000000077bff
12-24 18:34:06.186 3931 3931 F DEBUG : #05 0x00000075447a9b6b /system/lib64/libhidlbase.so+0x0000000000075b6b
12-24 18:34:06.186 3931 3931 F DEBUG : #06 0x00000075447a8f4b /system/lib64/libhidlbase.so+0x0000000000074f4b
12-24 18:34:06.186 3931 3931 F DEBUG : #07 0x00000075447a8ed3 /system/lib64/libhidlbase.so+0x0000000000074ed3
12-24 18:34:06.186 3931 3931 F DEBUG : #08 0x000000752acec227 /system/lib64/libutils.so+0x0000000000012227
12-24 18:34:06.186 3931 3931 F DEBUG : #09 0x000000754785046f /system/lib64/libandroid_runtime.so+0x00000000000c146f
12-24 18:34:06.186 3931 3931 F DEBUG : #10 0x000000752acebacf /system/lib64/libutils.so+0x0000000000011acf
12-24 18:34:06.186 3931 3931 F DEBUG : #11 0x000000752afbb33b /apex/com.android.runtime/lib64/bionic/libc.so+0x00000000000b333b
12-24 18:34:06.186 3931 3931 F DEBUG : #12 0x000000752af596cb /apex/com.android.runtime/lib64/bionic/libc.so+0x00000000000516cb
12-24 18:34:06.186 3931 3931 F DEBUG :
12-24 18:34:06.186 3931 3931 F DEBUG : '
12-24 18:34:06.186 3931 3931 F DEBUG : x0 0000000000000000 x1 0000000000000f15 x2 0000000000000006 x3 000000720b133080
12-24 18:34:06.186 3931 3931 F DEBUG : x4 606b5e686267394b x5 606b5e686267394b x6 606b5e686267394b x7 7f7f7f7f7f7f7f7f
12-24 18:34:06.186 3931 3931 F DEBUG : x8 00000000000000f0 x9 000000752af2a0b0 x10 ffffff00fffffbdf x11 0000000000000001
12-24 18:34:06.186 3931 3931 F DEBUG : x12 000000720b132d65 x13 000000720b1330f6 x14 00000072232f43f9 x15 0000000000000054
12-24 18:34:06.186 3931 3931 F DEBUG : x16 000000752afca050 x17 000000752afa6600 x18 000000720aae4000 x19 00000000000000ac
12-24 18:34:06.186 3931 3931 F DEBUG : x20 0000000000000cb6 x21 00000000000000b2 x22 0000000000000f15 x23 00000000ffffffff
12-24 18:34:06.186 3931 3931 F DEBUG : x24 00000072233c1000 x25 000000752afcc330 x26 000000720b134000 x27 000000720b133178
12-24 18:34:06.186 3931 3931 F DEBUG : x28 00000000000fc000 x29 000000720b133100
12-24 18:34:06.186 3931 3931 F DEBUG : lr 000000752af57dfc sp 000000720b133060 pc 000000752af57e2c pst 0000000000000000
12-24 18:34:06.186 3931 3931 F DEBUG : backtrace:
12-24 18:34:06.186 3931 3931 F DEBUG : #00 pc 000000000004fe2c /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) (BuildId: 2c33b61ae6a1176381005b83b27c2227)
12-24 18:34:06.186 3931 3931 F DEBUG : #01 pc 00000000000a2688 /system/lib64/libchrome.so (base::debug::BreakDebugger()+40) (BuildId: e8b35abb5abcf0c428c4ba78fb2a8782)
12-24 18:34:06.186 3931 3931 F DEBUG : #02 pc 00000000000bc384 /system/lib64/libchrome.so (logging::LogMessage::~LogMessage()+1308) (BuildId: e8b35abb5abcf0c428c4ba78fb2a8782)
12-24 18:34:06.186 3931 3931 F DEBUG : #03 pc 0000000000300dd8 /system/lib64/libbluetooth.so (hci_root_inflamed_abort()+288) (BuildId: 092522d42d1766f5f558baed58335c17)
12-24 18:34:06.186 3931 3931 F DEBUG : #04 pc 0000000000056260 /system/lib64/libhidlbase.so (android::hardware::hidl_binder_death_recipient::binderDied(android::wp<android::hardware::IBinder> const&)+112) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #05 pc 0000000000077cfc /system/lib64/libhidlbase.so (android::hardware::BpHwBinder::reportOneDeath(android::hardware::BpHwBinder::Obituary const&)+124) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #06 pc 0000000000077bfc /system/lib64/libhidlbase.so (android::hardware::BpHwBinder::sendObituary()+196) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #07 pc 0000000000075b68 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+2880) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #08 pc 0000000000074f48 /system/lib64/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+96) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #09 pc 0000000000074ed0 /system/lib64/libhidlbase.so (android::hardware::poolThread::threadLoop()+24) (BuildId: 2591ba3f2af0543158f951c258ba6234)
12-24 18:34:06.186 3931 3931 F DEBUG : #10 pc 0000000000012224 /system/lib64/libutils.so (android:🧵:_threadLoop(void*)+260) (BuildId: 19e4a71f7e74f619ba03e51c9be95bb7)
12-24 18:34:06.187 3931 3931 F DEBUG : #11 pc 00000000000c146c /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) (BuildId: a48f54116c1d9142dc5494bc29512bfd)
12-24 18:34:06.187 3931 3931 F DEBUG : #12 pc 0000000000011acc /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+404) (BuildId: 19e4a71f7e74f619ba03e51c9be95bb7)
12-24 18:34:06.187 3931 3931 F DEBUG : #13 pc 00000000000b3338 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 2c33b61ae6a1176381005b83b27c2227)
12-24 18:34:06.187 3931 3931 F DEBUG : #14 pc 00000000000516c8 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 2c33b61ae6a1176381005b83b27c2227)
12-24 18:34:06.236 1309 1643 E BluetoothManagerService: MESSAGE_BLUETOOTH_SERVICE_DISCONNECTED(1)
12-24 18:34:06.237 1309 1480 W ActivityManager: Scheduling restart of crashed service com.android.bluetooth/.btservice.AdapterService in 1000ms for connection
12-24 18:34:06.241 1309 1908 E NativeTombstoneManager: Tombstone's UID (1002) not an app, ignoring
12-24 18:34:06.637 1309 1713 E AppHibernationService: Attempt to call isHibernatingForUser on stopped or nonexistent user 0
12-24 18:34:06.638 1309 1655 W ActivityManager: com.android.bluetooth inode == 0 (b/152760674)
12-24 18:34:06.866 1309 1713 E AppHibernationService: Attempt to call isHibernatingForUser on stopped or nonexistent user 0
12-24 18:34:07.567 1309 1713 E AppHibernationService: Attempt to call isHibernatingForUser on stopped or nonexistent user 0
12-24 18:34:07.568 1309 1655 W ActivityManager: com.android.smspush inode == 0 (b/152760674)
12-24 18:34:07.578 1309 1713 E AppHibernationService: Attempt to call isHibernatingForUser on stopped or nonexistent user 0
12-24 18:34:07.580 1309 1713 E AppHibernationService: Attempt to call isHibernatingForUser on stopped or nonexistent user 0

Tombstone Log: https://gist.github.com/WJ3ffrey/6403a854b97a12d0109c6d1965b07b14


No idea how to deg this. What I think is happening is that the bluetooth hal is dying because /data/misc/bluedroid/bt_config.conf is missing but I don't know how the system even populates that file so I really don't know what could be the fix to this
Another thing might be that wlan_mac.bin and bt.mac files don't exist on the persist partition causing errors like
12-24 23:05:01.693 5844 5915 E [email protected]_address: Failed to open /data/vendor/mac_addr/bt.mac: No such file or directory
12-24 18:33:58.421 0 0 E ueventd : firmware: attempted /etc/firmware/wlan/qca_cld/wlan_mac.bin, open failed: No such file or directory
12-24 18:33:58.421 0 0 E ueventd : firmware: attempted /odm/firmware/wlan/qca_cld/wlan_mac.bin, open failed: No such file or directory
12-24 18:33:58.421 0 0 E ueventd : firmware: attempted /vendor/firmware/wlan/qca_cld/wlan_mac.bin, open failed: No such file or directory
12-24 18:33:58.421 0 0 E ueventd : firmware: attempted /firmware/image/wlan/qca_cld/wlan_mac.bin, open failed: No such file or directory
12-24 18:33:58.421 0 0 E ueventd : firmware: attempted /vendor/firmware_mnt/image/wlan/qca_cld/wlan_mac.bin, open failed: No such file or directory

Do you also get these on your crDroid builds?
 
Last edited:

Top Liked Posts