[ROM][OFFICIAL][begonia][11.0] crDroidAndroid v7.x - Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe

{
"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/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
WARNING: It is highly recommended to come from global miui 12.5.3 and to follow steps properly, expecially by using recommended recoveries to avoid bricks or any kind of errors !
Use this recovery to format data
Format Data
Change to this recovery to flash the rom
Wipe system, dalvik, cache, vendor
Install Rom
Install gapps (Optional)
Reboot
Update installation:
Reboot to recovery
Wipe Dalvik/Cache
Install rom
Install gapps (Optional)
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Device sources: https://github.com/begonia-dev
Download:
ROM https://crdroid.net/begonia
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/11.0/changelog_begonia.txt
Known issues:
* You tell me
Visit official website @ crDroid.net
DarkJoker360 Telegram Updates
crDroid Community Telegram
crDroid Updates Channel
Donations

---

Reserved

---

it's necessary to flash your recovery first?

---

Roury said:
it's necessary to flash your recovery first?
Click to expand...
Click to collapse
Nope if you understand how it works and can solve errors. Only need brp 3.0 (recommend) or twrp for 12.5fw enough.

---

Users of this ROM, how is the idle battery life?
Every 12.5 Custom ROM I try is draining battery even with a custom kernel.
Compass.

---

Compass Linux said:
Users of this ROM, how is the idle battery life?
Every 12.5 Custom ROM I try is draining battery even with a custom kernel.
Compass.
Click to expand...
Click to collapse
I'm not sure what you consider "non-draining", but I'm getting 48h+ battery life (with ~7h SOT) on one charging... but on PE, stock kernel

---

parkourz said:
I'm not sure what you consider "non-draining", but I'm getting 48h+ battery life (with ~7h SOT) on one charging... but on PE, stock kernel
Click to expand...
Click to collapse
With 12.0 Custom Roms: ~4 days battery life (80% charge)
With 12.5 Custom Roms: ~2 days battery life (80% charge)
So my battery life halved from 12.0 to 12.5.
Compass.

---

parkourz said:
I'm not sure what you consider "non-draining", but I'm getting 48h+ battery life (with ~7h SOT) on one charging... but on PE, stock kernel
Click to expand...
Click to collapse
If you wat bb and not play game. Try 12fw based custom roms + QK L Proton + EAS. Last time i can reach 15h SOT /100 with play some normal game (Tft), Youtube, Telegram, music. And if you want play game, just dirty flash QK N for performance then flash L again for bb. Lastest QK supported new selfie cam.

---

Finly rom with out hardbrike my phone i hardbrike my 2 time and pad 60$ naw finly room graet but i have littel ask how on alwys on disply

---

And any one have gcam work smothe on theis rom ?

---

Gouda998 said:
Finly rom with out hardbrike my phone i hardbrike my 2 time and pad 60$ naw finly room graet but i have littel ask how on alwys on disply
Click to expand...
Click to collapse
Why spend that much? Just join Telegram, they have free unbrick method and you can ask if you have errors. Even you ask other to help you, dont need spend that much. Free or just 5-10$ they will help you online. And if you can learn something from that, you can do it by yourself.

---

Sorry for a noob question.
I was on stock MIUI 11 Android 9, then I flashed Crdroid 7.2 (CFW ROM).
Now it shows a new update 7.11.
Can I dirty flash it or it will broke something?
I have TWRP 3.4.0_10-Metadata installed on it.
I can not flash stock MIUI 12.5 because of locked Mi account.
Thank you for answer.

---

DVele said:
Sorry for a noob question.
I was on stock MIUI 11 Android 9, then I flashed Crdroid 7.2 (CFW ROM).
Now it shows a new update 7.11.
Can I dirty flash it or it will broke something?
I have TWRP 3.4.0_10-Metadata installed on it.
I can not flash stock MIUI 12.5 because of locked Mi account.
Thank you for answer.
Click to expand...
Click to collapse
This is offical rom based on 12.5fw (step need miui 12.5.x). So i think you cant dirty flash it. And you have some ways to flash stock. You can flash stock then Force turn off by press and go in Fastboot when Miui show up, you dont need to finish boot into Miui setting. Or you can edit Flash_all file delete flash system code. Or flash by Sp flash tool. Many options without boot in Miui.

---

Well, I've installed this and now I have to wait around a week with normal usage to see how the battery drain goes.
Time will tell.
It's using a recent kernel (4.14.250) so that's a plus.
Compass.

---

DVele said:
Sorry for a noob question.
I was on stock MIUI 11 Android 9, then I flashed Crdroid 7.2 (CFW ROM).
Now it shows a new update 7.11.
Can I dirty flash it or it will broke something?
I have TWRP 3.4.0_10-Metadata installed on it.
I can not flash stock MIUI 12.5 because of locked Mi account.
Thank you for answer.
Click to expand...
Click to collapse
Don't dirty flash!
You're on CFW and your recovery is quite old.
You'll risk a hard brick.
Compass.

---

Compass Linux said:
Don't dirty flash!
You're on CFW and your recovery is quite old.
You'll risk a hard brick.
Compass.
Click to expand...
Click to collapse
So the right steps for me are:
1. Flash MIUI 12.5.3 via fastboot.
2. Reboot to fastboot again (because of locked Mi account) and flash recovery file from OP.
3. Reboot to recovery and flash Crdroid.
4. Format data.
5. Reboot to system.
Am I right?

---

DVele said:
So the right steps for me are:
1. Flash MIUI 12.5.3 via fastboot.
2. Reboot to fastboot again (because of locked Mi account) and flash recovery file from OP.
3. Reboot to recovery and flash Crdroid.
4. Format data.
5. Reboot to system.
Am I right?
Click to expand...
Click to collapse
I've never had issues with a locked Mi Account, but below are the steps I used:
Boot to fastboot mode;
Flash MIUI 12.5.1 Fastboot ROM (global doesn't have a Fastboot 12.5.3 yet, only recovery);
Boot to fastboot mode;
Flash BRP3.5.2v3.0 (I extracted recovery.img from the zip and used that);
Boot to recovery;
Wipe system, dalvik, cache and vendor (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Format data (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Flash crDroid;
Flash Open GApps (I used the latest arm64-11 nano; it took a while to flash but it worked);
Reboot to system;
Install the Magisk v23.0 apk;
Boot to recovery;
Flash the Magisk v23.0 zip (flashing the apk should also work; same file);
Boot to system;
Check the Magisk app if root is installed (it is).
I think Kirasu2080 is correct. You can ignore setting up MIUI therefore no Mi Account issue.
Compass.

---

Compass Linux said:
I've never had issues with a locked Mi Account, but below are the steps I used:
Boot to fastboot mode;
Flash MIUI 12.5.1 Fastboot ROM (global doesn't have a Fastboot 12.5.3 yet, only recovery);
Boot to fastboot mode;
Flash BRP3.5.2v3.0 (I extracted recovery.img from the zip and used that);
Boot to recovery;
Flash crDroid;
Flash Open GApps (I used the latest arm64-11 nano; it took a while to flash but it worked);
Wipe system, dalvik, cache and vendor (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Format data (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Reboot to system;
Install the Magisk v23.0 apk;
Boot to recovery;
Flash the Magisk v23.0 zip (flashing the apk should also work; same file);
Boot to system;
Check the Magisk app if root is installed (it is).
I think Kirasu2080 is correct. You can ignore setting up MIUI therefore no Mi Account issue.
Compass.
Click to expand...
Click to collapse
Thank you so much for a detailed guide. I do not have time to flash it today, but I hope it will all work just fine. And I hope it will not get bricked or something like that.

---

Compass Linux said:
I've never had issues with a locked Mi Account, but below are the steps I used:
Boot to fastboot mode;
Flash MIUI 12.5.1 Fastboot ROM (global doesn't have a Fastboot 12.5.3 yet, only recovery);
Boot to fastboot mode;
Flash BRP3.5.2v3.0 (I extracted recovery.img from the zip and used that);
Boot to recovery;
Flash crDroid;
Flash Open GApps (I used the latest arm64-11 nano; it took a while to flash but it worked);
Wipe system, dalvik, cache and vendor (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Format data (I think this is unnecessary because I flashed MIUI 12.5.1; did it anyway);
Reboot to system;
Install the Magisk v23.0 apk;
Boot to recovery;
Flash the Magisk v23.0 zip (flashing the apk should also work; same file);
Boot to system;
Check the Magisk app if root is installed (it is).
I think Kirasu2080 is correct. You can ignore setting up MIUI therefore no Mi Account issue.
Compass.
Click to expand...
Click to collapse
1/Check your steps again. Why Wipe after flash rom?
2/It maybe end with format error because of encryption.

---

1. Go in Fastboot mode, flash Miui 12.5.x fastboot rom (any kind but begonia recommend)
2. Go in Fastboot mode, download and flash Brp 3.5.2 v3.0 by run file 1.Flash...bat, it will automatically reboot in twrp.
3. Wipe>Advanced Wipe>Dalvik, Cache, System, Data, Vendor. Reboot>Recovery.
4. Wipe>Format data>yes. Reboot>Recovery.
(If you dont have encryption Format data error, just wipe in step 3 and go direct to step 5)
(If encryption error still cant fix, go in Fastboot and use command "fastboot -w")
5. Install>Flash custom rom.
6. Install>Flash Gapps (optional)
7. Advanced>Disable ForceEncryption (optional)
8. Wipe>Format data>yes>Reboot system.
If you need Magisk:
9. Go in Twrp. Advanced>Magisk install>Reboot system.
If you have bootloop after flash Magisk:
10. Go in twrp. Advanced>Patch vbmeta>Reboot system.