[ROM][12.1][OFFICIAL][LMI] crDroid v8.14 [23.03.2023] - Xiaomi Poco F2 Pro (Redmi K30 Pro) ROMs, Kernels,

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps : Nikgapps and Flamegapps are both tested
Magisk 23.0 for root (after first boot) - (Download from here)
First time installation:
make use of 3.6.0_11-RedmiK30Pro_v3.0.3_A12-lmi-skkk_0b4ac24c.img or your preferred one
boot recovery
format & reboot recovery
flash Firmware (minimum requirement 12.5.3) (skip if you are on 12.5.3 or later)
flash crDroid
reboot recovery
(optional) flash Gapps
(optional) flash Magisk
boot system
Update installation: (if on cr8 already)
boot recovery
flash crDroid
boot system
Sources:
ROM: https://github.com/crdroidandroid
Device Trees: lmi + common
Kernel: Quantic kernel thx @GtrCraft
Download:
ROM: LMI
Changelog: LMI
LATEST BUILD AND INSTRUCTIONS
Known issues:
...
ROM OS Version: 12.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, min. miu v12.5.x
Status: stable
Sec. Patches : 2023.03.05
Created : 2022.01.18
Last Updated : 2023.03.23
Thnx to :
@Schnedi
@Ayrton990
Visit official website @ crDroid.net
crDroid LMI Telegram
crDroid Community Telegram
crDroid Updates Channel
Donations are appreciated to continue development

---

Changelog: LMI

---

Thx boss !!!!!

---

This is one of the ROMs that I've been anticipating to have an A12 update. Thank you for keeping lmi alive!

---

Does VOLTE work here?

---

Can someone please confirm if the low microphone volume recording bug for WhatsApp voice notes etc is present on this rom, like it is for the A11 crdroid?

---

Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!

---

lafa011 said:
Hi to all of you!
Great ROM with all the great looks and feel but as in 7.13 version I am not able to get the mobile data to work...
Anyway, big thanks to the developers for all the effort!
Click to expand...
Click to collapse
Have you tried manually setting up the APN in Settings?

---

I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid

---

woodencase01 said:
I was looking forward to this update, Thanks for your hard work!
I'm facing a bootloop problem for some reasons...
I once successfully installed it, but realized NikkGapp didn't use my config, so I went back into TWRP to run it again and use my config.
I didn't realized it at this time (now I know), but TWRP didn't ask for any pattern unlock. The sd-card wasn't detected, so I tried a couple of things to solve it, and this is where it starts to get problematic. I did the sd-card switch from ext2 to ext4.
From that point, I got into a boot loop. I tried to flash the CrDroid rom again, but it won't work.
I then flashed the global original image to start fresh, but TWRP still won't ask for pattern to unlock, thus doing the flashing again didn't work...
Do you have any idea how I can fix it? I'm back on MIUI and I already miss CrDroid
Click to expand...
Click to collapse
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions

---

thetta-reddast said:
After getting bootloops from installing different roms I learned this: disable the screen lock (Settings->Security->Screen lock->None) before flashing anything. This way TWRP should be able to mount the partitions
Click to expand...
Click to collapse
Thanks for your help.
I disabled the screen lock, but sadly it didn't work.
I get errors messages such as:
I:File Based Encryption is present
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
fscrypt_init_user0 returned fail
Unable to decrypt FBE device.
If your device is not encrypted, decrypting the FEB device will fail.
E:fde::get_crypt_ftr_and_key::Unexpected value for crypto key location:
E:Error getting crypt footer and keyE:Could not get footerDecrypt process ended with signal: 11
Failed to decrypt data.
Unable to decrypt with default password. You may need to perform a Format Data.
and
Android Rescue Party trigger! Possible solutions? Either:
1. Wipe caches, and/or
2. Format data, and/or
3. Clean-flash your ROM.
The reported problem is:
'set_policy_failed:/data/system'
Not sure what to do...

---

I tried changing the data format to ext4, then format it through ADB, didn't work.
My current error message is "init_user0_failed". I also still have the "Rescue Party trigger!" message.
EDIT:
I managed to boot by formatting DATA after flashing, but the OS seems to be missing a lot of stuff.
EDIT 2:
Ok, started the clean flashing process again, still got in bootloop. Tried formatting data again, and it worked!

---

batuken said:
Have you tried manually setting up the APN in Settings?
Click to expand...
Click to collapse
Thank you for your reply. I did not try changing the APN settings but tried MIUI stable 12.2.6.0 needed for flashing the 7.13 crDroid and it works there out of the box. Maybe changing the APN would work but I gave up and get back to EU version instead, which is ok for me except for custom launcher like Nova since I cannot get around the home buttons appearing/dissapearing when I use gestures with Nova launcher... That was the first thing that led me to trying crDroid

---

Спасибо за ROM!!!
----------
MOD EDIT: English Translation Below
Thanks for the ROM!!!

---

tell me from which version of MIUI you need to flash crdroid 8

---

Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...

---

Lyngze said:
Can anyone confirm wether crdroid has issues with high security apps requiring "official" builds?
For example the Danish verification service MitID (https://play.google.com/store/apps/details?id=dk.mitid.app.android)
App would open to only display that "device is rooted" on Spark A12 rom...
Click to expand...
Click to collapse
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.

---

woodencase01 said:
I have the same problem with our COVID app, I simply flashed Magisk, then once I'm in the OS, you can install MagiskHide, it also works for Google Pay on rooted phones. Make sure to clear the app cache when activating MagiskHide, otherwise the message about the rooting will stay.
Click to expand...
Click to collapse
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?

---

I'm currently using "NikGapps-full-arm64-12-20211227-signed" as GAPP, but sadly, chrome keeps freezing. I'm currently using a different browser. Has anyone a fix for this?

---

Lyngze said:
This was without root. Google Pay and other banking apps and such worked. But a few had some extra checks apart from SafetyNet and such.
I would rather not root and mess with magisk if it could be avoided.
I don't have any need for root and would rather not install too much third party stuff with potential security risks.
Did Google Pay not work for you without root and magisk hide either?
Click to expand...
Click to collapse
My device is rooted since day one. I don't know how to flash a custom ROM without first rooting.
But yes, without MagiskHide, I couldn't use Google Pay. Haven't found another way to make it work.