[ROM][13][BERYLLIUM] crDroid v9.5 [19.06.2023] - Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other

{
"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/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (from download page, recovery button)
NikGapps core (Download from here - note that you may also need setup wizard addon if you rely on Google restore)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Via recovery
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium/9
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal

Here we go again!
Thank you very much Gabriel for keeping it alive

This is it, firstly thanks for taking our f1 device to a higher level, secondly @gwolfu @Retrial how to update from crdroid A12 latest build, but using official twrp, I have no problem with decrypting data or anything like that, as long as official twrp stays where it should be and don't lose data, thank you very much crdroid team and especially for you @gwolfu thanks again to everyone here

Artemis008 said:
This is it, firstly thanks for taking our f1 device to a higher level, secondly @gwolfu @Retrial how to update from crdroid A12 latest build, but using official twrp, I have no problem with decrypting data or anything like that, as long as official twrp stays where it should be and don't lose data, thank you very much crdroid team and especially for you @gwolfu thanks again to everyone here
Click to expand...
Click to collapse
I don't know how your official twrp is able to decrypt, encrypted ROMs since it's not working. Are u sure encrypted?
Recommended is to do Clean Install from one Android version to another. However you can try my Dirty Installation guide below.
Official way of installation via crDroid recovery can be found in OP.
Installation Guide:
Clean Install via TWRP:
Backup your data.
Downland TWRP by REIGNZ v2 (A12_System_Ext version - Current Bugs & Workarounds), crDroid ROM, A13 GApps of your choice and optional crDroid recovery if you want to use that later.
Boot, flash and reboot to TWRP.
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (need due to a current issue with twrp by reignz) and then Format data > type yes.
Transfer the ROM while you are connected and into TWRP from PC to Device. (TWRP by REIGNZ3 have issue, if PC doesn't recognize the device, press in twrp menu, advanced > file manager > and find and select sdcard folder aka Internal Storage > go back and now pc should be able to recognize the device)
If you have SDcard or USB OTG you can also use that.
Flash ROM, GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash crDroid recovery.
[Optional] If you want to stay decrypted, use TWRP by REIGNZ but based on A9. Mount Vendor and flash DFE A13. Do not use OTA if you are decrypted, update via dirty installation.
Reboot and Enjoy!
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install.
Dirty Installation via TWRP:
Manually Upgrade/Update the ROM
Download the latest build of crDroid ROM, A13 GApps of your choice and use TWRP by REIGNZ v2 (A12_System_Ext version - Current Bugs & Workarounds).
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM, GApps.
[Optional] If you are decrypted, Mount Vendor and flash DFE A13.
Reboot and Enjoy!
Notes:
If you want to be encrypted, recommended is to do one Clean Install according to guide and afterwards you can do OTA updates.
If you are decrypted and you want to stay decrypted, do Dirty Install according to guide and do not use OTA.
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.

I intend to try this amazing Rom, but first I would like to know if Nandbackup is working ok in twrp by reignz? I remember reading a post from someone saying they couldn't restore the nandbackup created with this twrp. I'm currently on Awaken 2.10

Thanks for the Rom it works fine just there is this bug in the qs menu
i already did a clean flash

Retrial said:
I don't know how your official twrp is able to decrypt, encrypted ROMs since it's not working. Are u sure encrypted?
Recommended is to do Clean Install from one Android version to another. However you can try my Dirty Installation guide below.
Official way of installation via crDroid recovery can be found in OP.
Installation Guide:
Clean Install via TWRP:
Backup your data.
Downland TWRP by REIGNZ (A12_System_Ext version - Current Bugs & Workarounds), crDroid ROM, A13 GApps of your choice and optional crDroid recovery if you want to use that later.
Boot, flash and reboot to TWRP.
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (need due to a current issue with twrp by reignz) and then Format data > type yes.
Transfer the ROM while you are connected and into TWRP from PC to Device. (TWRP by REIGNZ3 have issue, if PC doesn't recognize the device, press in twrp menu, advanced > file manager > and find and select sdcard folder aka Internal Storage > go back and now pc should be able to recognize the device)
If you have SDcard or USB OTG you can also use that.
Flash ROM, GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash crDroid recovery.
[Optional] If you want to stay decrypted, Mount Vendor and flash DFE A13. Do not use OTA if you are decrypted, update via dirty installation.
Reboot and Enjoy!
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install.
Dirty Installation via TWRP:
Manually Upgrade/Update the ROM
Download the latest build of crDroid ROM, A13 GApps of your choice and use TWRP by REIGNZ (A12_System_Ext version - Current Bugs & Workarounds).
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM, GApps.
[Optional] If you are decrypted, Mount Vendor and flash DFE A13.
Reboot and Enjoy!
Notes:
If you want to be encrypted, recommended is to do one Clean Install according to guide and afterwards you can do OTA updates.
If you are decrypted and you want to stay decrypted, do Dirty Install according to guide and do not use OTA.
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.
Click to expand...
Click to collapse
previously on crdroid a12 I remember your words @Retrial that official twrp doesn't support encrypted rom, that's why I decided to install DFE after updating (dirty flash) via official twrp, I'm always on a decrypted rom, so can I do a dirty update from crdroid a12 to crdroid a13 without replacing the official twrp, I have no problem with encryption things, and it doesn't matter if the ota update only displays the notification, because after that I also update it via twrp not via ota.

Artemis008 said:
previously on crdroid a12 I remember your words @Retrial that official twrp doesn't support encrypted rom, that's why I decided to install DFE after updating (dirty flash) via official twrp, I'm always on a decrypted rom, so can I do a dirty update from crdroid a12 to crdroid a13 without replacing the official twrp, I have no problem with encryption things, and it doesn't matter if the ota update only displays the notification, because after that I also update it via twrp not via ota.
Click to expand...
Click to collapse
Yes Official TWRP doesn't support decryption for A12+ encrypted ROMs.
However TWRP by REIGNZ support it.
You can try to upgrade following the dirty installation guide along with DFE but keep in mind this may result bugs/glitches and even bootloop since you upgrading to another android version.
Recommended is to clean install, but if you try to upgrade via dirty installation take backups in case of bootloops.

Retrial said:
Yes Official TWRP doesn't support decryption for A12+ encrypted ROMs.
However TWRP by REIGNZ support it.
You can try to upgrade following the dirty installation guide along with DFE but keep in mind this may result bugs/glitches and even bootloop since you upgrading to another android version.
Recommended is to clean install, but if you try to upgrade via dirty installation take backups in case of bootloops.
Click to expand...
Click to collapse
I'll try it, if it fails it means the only way is clean flash, okay I'll let you know if there are bugs, or a bootloop occurs

Is Selinux enforcing or permissive?

Did a clean wipe and installed CRDroid 9. Everything working well so far, I got the same bug as @ok689 as wwll

lepidas said:
Is Selinux enforcing or permissive?
Click to expand...
Click to collapse
Enforcing
sunnybhai said:
Did a clean wipe and installed CRDroid 9. Everything working well so far, I got the same bug as @ok689 as wwll
Click to expand...
Click to collapse
Will get fixed in future updates

freshly flashed, moved from 7.15 with clean flash. so far works good, sometimes laggy but mostly nice working. big Thanks.

I also installed it a few days ago, works very fine. Thanks a lot =)
One question - should the QR Scanner of A13 in QS menu work on our poco f1? Or is their a way to activate it?

Hi,
thank you for the amazing work. Until now everything works fine on my f1.
The only thing I miss is the Poco F1 camera.
Is there any way to get it on Android 13.
Or do you have another option that is similar or better ?
Thank you very much.
Schlapperklange

Schlapperklange said:
Hi,
thank you for the amazing work. Until now everything works fine on my f1.
The only thing I miss is the Poco F1 camera.
Is there any way to get it on Android 13.
Or do you have another option that is similar or better ?
Thank you very much.
Schlapperklange
Click to expand...
Click to collapse
It works very well with this rom, and it has many options
Cam
Link to the website
And if you are not convinced, you can look here, and in the cam section you have a few cameras to try
Greetings!!!

will you make face unlock? in crdroid 8 it exist, but now i cant find it

PRIFAK said:
will you make face unlock? in crdroid 8 it exist, but now i cant find it
Click to expand...
Click to collapse
Sure, but take your time. This thing requires some patience!)

Unfortunately I have some issues since a few hours with some apps.
After opening one app it closes immediately.
Another problem i have with my email app. I open the app, then i open an email and immediately the mail closes and switch back to the main email app screen.
Both apps worked without any issues till some hours.
I already restarted the phone, cleaned cache and data - also without any success.
Is there anything I can try? Otherwise I will wait for the next update, hopefully the issues are gone then...
Thanks in advance

Hello
I have a problem with wifi on this rom (both 28th October and 5th November)
Since today I can not turn on wifi.
Does anyone have that problem?
Thanks in advance.

Related

RN3 Pro SD Kenzo - flashing Lineage OS?

Hi everyone,
a quick question.
I am running a:
RN3 Pro SD Kenzo
8.0.6.0 Global Stable firmware ( Lollipop ), unofficial unlock
ZCX TWRP
... yeah, I am still on Lollipop. Reason is that this firmware, at the time of flashing, proved to be the most stable, so I kept it. It still is the best Xiaomi firmware I tested, out all of them, but now, I would like to test out Lineage OS
What would be the fastest way for me to flash the latest Lineage OS on this phone, while keeping the bootloader unlocked?
Can I just wipe the phone, add Lineage and GApps and flash it through recovery?
make sure you have downloaded latest firmware, LOS rom & gapps....next steps is backup your current rom & go flashing.
twrp > wipe > wipe dalvik, system, data & cache > install latest firmware > install LOS rom > install gapps > reboot > done
here is firmware you have needed
Thank you for taking the time to assist me.
Firmware link is not working, sadly.
... so, basically, if I get this right:
1. boot into my TWRP
2. wipe dalvik/system/data/cache
3. after wiping is done, flash/install the latest CM 14.1 firmware without rebooting, select wipe
4. after firmware finishes flashing/installing, flash/install LOS ( without rebooting ), select wipe
5. after that, flash/install GApps, select wipe
6. reboot, and that's it?
Any special steps I should take to keep my unofficial bootloader unlock, or that does not matter with LOS?
EDITED POST FOR CLARITY AND FUTURE REFERENCE.
Tomo123 said:
Thank you for taking the time to assist me.
Firmware link is not working, sadly.
... so, basically, if I get this right:
1. boot into my TWRP
2. wipe dalvik/system/data/cache
3. after wiping is done, flash/install the latest MIUI firmware without rebooting
4. after MIUI finishes flashing/installing, flash/install LOS ( without rebooting )
5. after that, flash/install GApps
6. reboot, and that's it?
Do I flash latest stable or developer firmware in step 3?
Any special steps I should take to keep my unofficial bootloader unlock, or that does not matter with LOS?
Click to expand...
Click to collapse
sorry...find it here
https://forum.xda-developers.com/redmi-note-3/how-to/cm14-14-1-aosp-n-firmware-kenzo-kate-t3507789
that is right...follow my instructions & no need to worrie about bootloader
Thank you for the link. But, the firmware you provided the link for is only around 46MB. Is that right?
Thank you for the asistance. Everything is flashed, and working.
Additional step I had to do was to flash the camera fix from here:
https://forum.xda-developers.com/re...niversal-camera-binary-patch-kenzo-n-t3572779
... and done.
Now, as for the root access, only option I have available through Developer options is root through ADB. Do I download the root package from here:
https://download.lineageos.org/extras
... or is there another method for RN3Pro SD LineageOS?
Downloaded LOS root package. I am set

is it safe to flash MIUI global 10 fastboot rom with twrp?

hello,
so I was just wondering is it safe to flash MIUI 10 global rom with twrp? I know that it will probably replace the twrp with stock recovery, but it is easily fixed. I had to restore old backup and right now I'm on MIUI beta rom but with beta roms being shut down starting from 1st july, I just want to convert to the latest MIUI global rom which is avilable here on thier offical site and it is called Version: V10.3.4.0.PEJMIXM (MIUI10)
so again my question:
1. is it safe to flash this rom with TWRP?
2. will i need fastboot zip file if I choose to flash with TWRP?
3. or can I just download the normal zip and flash it through local update feature? please take note that twrp is installed on my phone
so that's all.. thanks for your time:good:
alifarhad said:
hello,
so I was just wondering is it safe to flash MIUI 10 global rom with twrp? I know that it will probably replace the twrp with stock recovery, but it is easily fixed. I had to restore old backup and right now I'm on MIUI beta rom but with beta roms being shut down starting from 1st july, I just want to convert to the latest MIUI global rom which is avilable here on thier offical site and it is called Version: V10.3.4.0.PEJMIXM (MIUI10)
so again my question:
1. is it safe to flash this rom with TWRP?
2. will i need fastboot zip file if I choose to flash with TWRP?
3. or can I just download the normal zip and flash it through local update feature? please take note that twrp is installed on my phone
so that's all.. thanks for your time:good:
Click to expand...
Click to collapse
No,I recommend downloading the full (recovery) rom and flashing it in twrp, and then flashing the 'Disable Force Encryption' zip and later magisk if needed.., wipe dalvik cache & reboot
This way you don't lose twrp or anything else on your phone
Schumanzuar said:
No,I recommend downloading the full (recovery) rom and flashing it in twrp, and then flashing the 'Disable Force Encryption' zip and later magisk if needed.., wipe davlik cache & reboot
This way you don't lose twrp or anything else on your phone
Click to expand...
Click to collapse
Hi ethanks for your reply. What do you mean by full rom? Does twrp allow flashing miui global roms just like any other custom roms?
alifarhad said:
Hi ethanks for your reply. What do you mean by full rom? Does twrp allow flashing miui global roms just like any other custom roms?
Click to expand...
Click to collapse
Of course it does..
I'm talking about the full rom also called as recovery rom (Example :-
https://en.miui.com/getrom-355.html?m=yes&mobile=2
Visit this link to see the latest miui stable & beta ROMs for Poco f1, both of them are full ROMs aka recovery ROMs of the latest miui for Poco f1
1) I assume you have already unlocked bootloader etc..
First you have to have the essential files i.e the rom zip file you want to install, disable Force Encryption zip file, Magisk zip file (All files links will be available in the main Poco f1 thread)
2) Next you boot into twrp (Power + volume up button)
Next select install, navigate to the downloaded rom zip file and swipe to flash (DONT reboot after flash, click back)
3) Now again select install & now flash the disable Force Encryption zip file (This is very important & should be done during every rom flashing)
4) Next go back & flash Magisk for root
5) Wipe dalvik cache and reboot
Schumanzuar said:
Of course it does..
I'm talking about the full rom also called as recovery rom (Example :-
https://en.miui.com/getrom-355.html?m=yes&mobile=2
Visit this link to see the latest miui stable & beta ROMs for Poco f1, both of them are full ROMs aka recovery ROMs of the latest miui for Poco f1
1) I assume you have already unlocked bootloader etc..
First you have to have the essential files i.e the rom zip file you want to install, disable Force Encryption zip file, Magisk zip file (All files links will be available in the main Poco f1 thread)
2) Next you boot into twrp (Power + volume up button)
Next select install, navigate to the downloaded rom zip file and swipe to flash (DONT reboot after flash, click back)
3) Now again select install & now flash the disable Force Encryption zip file (This is very important & should be done during every rom flashing)
4) Next go back & flash Magisk for root
5) Wipe dalvik cache and reboot
Click to expand...
Click to collapse
Thanks it's much clearer now.
alifarhad said:
Thanks it's much clearer now.
Click to expand...
Click to collapse
Did you flash stable rom ?
And did you erase the data or internal storage?
I am on beta as well and have unlocked bootloader and twrp & magisk installed with Force encryption Disabled.
I want to switch to 10.3.5.0 Stable ROM.
But I don't know whether to erase Data partition or not.
gohil.mitul said:
Did you flash stable rom ?
And did you erase the data or internal storage?
I am on beta as well and have unlocked bootloader and twrp & magisk installed with Force encryption Disabled.
I want to switch to 10.3.5.0 Stable ROM.
But I don't know whether to erase Data partition or not.
Click to expand...
Click to collapse
1) Use migrate app from play store to take a backup of current phone app data, the backup is stored in a flashable zip format
2) Next boot to twrp, choose wipe and select davlik, cache, system, data later follow my steps in my previous comment to flash new rom
3) Set up phone etc, Make sure Magisk is installed properly
4) Next boot into twrp & flash the migrate zip file located in migrate folder, reboot after flashing, you will get a notification about migrate backup once rebooted, open it and restore everything or select choose to restore for selective restore of data

What is the need of "DisableForceEncryption_Treble.zip" and when to use it ?

What is the need of "DisableForceEncryption_Treble.zip" and when to use it ?
This is my first post on any XDA Forums, so forgive me for any mistakes.
I have a Poco F1 with the latest update [(MIUI Global 11.0.5.0 (stable)], TWRP recovery and Magisk v20.3 installed.
Some time ago I tried to root my phone (with the help of some youtube tutorial) using magisk and then I came across this file "DisableForceEncryption_Treble.zip" and I wanna know how & when to use it?
Do I have to flash it every time before flashing anything?
Ps: I am not able to attach the file link because I'm new to XDA.
Any help would be massively appreciated. :fingers-crossed:
ahmedsidd45 said:
This is my first post on any XDA Forums, so forgive me for any mistakes.
I have a Poco F1 with the latest update [(MIUI Global 11.0.5.0 (stable)], TWRP recovery and Magisk v20.3 installed.
Some time ago I tried to root my phone (with the help of some youtube tutorial) using magisk and then I came across this file "DisableForceEncryption_Treble.zip" and I wanna know how & when to use it?
Do I have to flash it every time before flashing anything?
Ps: I am not able to attach the file link because I'm new to XDA.
Any help would be massively appreciated. :fingers-crossed:
Click to expand...
Click to collapse
That file helps prevent forced encryption of user data. It's discussed here on XDA in the Xiaomi Poco F1 Firmware 11.0.5.0 9.7.11 ,Unlock Bootloader,TWRP Recovery and Root thread.
x2
ktmom said:
That file helps prevent forced encryption of user data. It's discussed here on XDA in the Xiaomi Poco F1 Firmware 11.0.5.0 9.7.11 ,Unlock Bootloader,TWRP Recovery and Root thread.
Click to expand...
Click to collapse
Thank you for the answer, it was indeed helpful.
All I could gather from various sources is that I have to flash the ForceEncryptionDisabler before flashing any custom ROM or even my stock rom i.e. MIUI
But all I wanna know is do I have to flash it before flashing other stuff? (for example, I want to flash the Youtube Vanced file)
Edit :
I tried it and turns out I don't need to install YouTube vanced using the recovery, I installed it as a module through Magisk.
WHENEVER
/vendor image is changed (eg from 9.26.7-9.0 to 10.x.x.x etc) / or reflashed; the decryption keys (assigned very first time when device was booted after your last flash) gets changed, and if you BOOT now without flashing DFE, your rom wont able to access the internal storage! and you must go back to twrp and FORMAT /data partition and you will LOOSE all the data in internal storage!
to over come this, you must flash DFE or flash custom roms having NO vendor image embeded! like carbon, linage16, RR7.0.2 etc, they were dependent on user to flash vendor image independetly, however currently almost all the roms have vendor image embeded! like if you flash Crdroid over havoc (android10 versions) , changes are you will be locked out at boot if you don't flash dfe ...
YasuHamed said:
WHENEVER
/vendor image is changed (eg from 9.26.7-9.0 to 10.x.x.x etc) / or reflashed; the decryption keys (assigned very first time when device was booted after your last flash) gets changed, and if you BOOT now without flashing DFE, your rom wont able to access the internal storage! and you must go back to twrp and FORMAT /data partition and you will LOOSE all the data in internal storage!
to over come this, you must flash DFE or flash custom roms having NO vendor image embeded! like carbon, linage16, RR7.0.2 etc, they were dependent on user to flash vendor image independetly, however currently almost all the roms have vendor image embeded! like if you flash Crdroid over havoc (android10 versions) , changes are you will be locked out at boot if you don't flash dfe ...
Click to expand...
Click to collapse
Thank you so much for the answer.
Cleared all my doubts !
And not before you have to flash DFE right after you flashed a rom with a vendor....
Question:
Is it necessary only for not MIUI based ROMs?
Since the beginning I've always had unlocked rooted (twrp, magisk) phone with Global stable, Global beta, EU ROMs and 've never used any kind of DFE. I reflashed beta ROMs may be 20 times without any problem. Even more, it was necessary to make clean flash only once, when I changed from Global stable to EU beta. All other times I did dirty flash.
slavau said:
Question:
Is it necessary only for not MIUI based ROMs?
Since the beginning I've always had unlocked rooted (twrp, magisk) phone with Global stable, Global beta, EU ROMs and 've never used any kind of DFE. I reflashed beta ROMs may be 20 times without any problem. Even more, it was necessary to make clean flash only once, when I changed from Global stable to EU beta. All other times I did dirty flash.
Click to expand...
Click to collapse
I found that I never needed to flash DFE after flashing xiaomi.eu on my F1 (only AOSP ROMs, including LOS). However, I flashed .eu on my RN7P and it became encrypted. I hadn't installed a custom ROM on it, and I formatted data prior to flashing .eu. I flash DFE after .eu every time now.
Pumpino said:
I found that I never needed to flash DFE after flashing xiaomi.eu on my F1 (only AOSP ROMs, including LOS). However, I flashed .eu on my RN7P and it became encrypted. I hadn't installed a custom ROM on it, and I formatted data prior to flashing .eu. I flash DFE after .eu every time now.
Click to expand...
Click to collapse
I've never had to flash DFE but I always used TWRP that supports en/decryption. In the beginning it was "TWRP 3.2.3-x Unofficial with working DECRYPTION", later official TWRP 3.3.0 for Poco.
So the routine is:
- boot to TWRP
- flash "magisk-uninstall"
- wipe Dalvik/Cache
- flash ROM (MIUI based)
- wipe Dalvik/Cache
- flash Magisk
- flash custom kernel (if any)
- reboot to system
slavau said:
I've never had to flash DFE but I always used TWRP that supports en/decryption. In the beginning it was "TWRP 3.2.3-x Unofficial with working DECRYPTION", later official TWRP 3.3.0 for Poco.
Click to expand...
Click to collapse
I use OrangeFox, so maybe that's why, though I do think that flashing a ROM with a custom vendor risks the phone being encrypted. I'm sure I experienced it when I previously used official TWRP and flashed certain ROMs. LOS was usually the main offender.
Pumpino said:
I use OrangeFox, so maybe that's why, though I do think that flashing a ROM with a custom vendor risks the phone being encrypted. I'm sure I experienced it when I previously used official TWRP and flashed certain ROMs. LOS was usually the main offender.
Click to expand...
Click to collapse
As far as I remember, when I tried OrangeFox (beginning of 2019?) it was necessary to flash DFE.
That was the reason why I moved to another recovery. Later they incorporated DFE into the OrangeFox and you are able to select whether to use DFE or not.
But I don't like the idea of DFE at all: why should I disable encryption instead of using compatible recovery?..
slavau said:
As far as I remember, when I tried OrangeFox (beginning of 2019?) it was necessary to flash DFE.
That was the reason why I moved to another recovery. Later they incorporated DFE into the OrangeFox and you are able to select whether to use DFE or not.
But I don't like the idea of DFE at all: why should I disable encryption instead of using compatible recovery?..
Click to expand...
Click to collapse
Well, my Redmi Note 7 Pro became encrypted when I flashed xiaomi.eu without DFE, only a matter of weeks ago. There was no option to flash DFE in OrangeFox-R10.0_2_b001-Beta.
I don't like the idea of DFE either. However, I blame ROMs for including a custom vendor; I might not understand it correctly, but I don't know why it's the responsibility of TWRP to prevent encryption.
Pumpino said:
Well, my Redmi Note 7 Pro became encrypted when I flashed xiaomi.eu without DFE, only a matter of weeks ago. There was no option to flash DFE in OrangeFox-R10.0_2_b001-Beta.
Click to expand...
Click to collapse
Since I have no OrangeFox installed, I can't check but I remember they advertised inbuilt DFE for a long time.
{
"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"
}
slavau said:
Since I have no OrangeFox installed, I can't check but I remember they advertised inbuilt DFE for a long time.
View attachment 4937133
Click to expand...
Click to collapse
I just booted into OrangeFox-R10.1_003-Beta on my Redmi Note 7 Pro. "Disable DM-Verity" and "Disable Forced Encryption" are not selected by default. That said, they're under the "MIUI OTA" menu, so I'm not sure if enabling them only influences MIUI based ROMs (and not AOSP).

[ROM][OFFICIAL][begonia][11.0] crDroidAndroid v7.x

{
"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.

After P.Experience Rom TWRP is gone and everything is encrypted

Hi. I installed Android 12 Pixel Experience rom and my TWRP gone after this. After installing the rom, TWRP replaced with Pixel Experience's own recovery mode. Currently, the ROM is installed and I can use it without any problems, but I cannot switch to a different ROM in any way. When I install TWRP with ADB, I cannot install the file named "DM Verity & ForceEncrypt disabler" because everything is encrypted. I do not use any passwords on the ROM (fingerprint, screen lock, etc.). I want to install new ROM so I need to make TWRP permanent and remove encryption on TWRP, because i can't see my files. As I said, the phone is can open and I can use it without problems. Looking forward to your help, thank you.
1) Backup everything
2) Install twrp and sideload the PE rom but don't boot into it
3) Flash the DFE (disable force encryption ) zip from twrp
4) Boot into the rom
Remember you won't get the ota updates if you disable the encryption and have to manually update the rom
easdasd617 said:
Hi. I installed Android 12 Pixel Experience rom and my TWRP gone after this. After installing the rom, TWRP replaced with Pixel Experience's own recovery mode. Currently, the ROM is installed and I can use it without any problems, but I cannot switch to a different ROM in any way. When I install TWRP with ADB, I cannot install the file named "DM Verity & ForceEncrypt disabler" because everything is encrypted. I do not use any passwords on the ROM (fingerprint, screen lock, etc.). I want to install new ROM so I need to make TWRP permanent and remove encryption on TWRP, because i can't see my files. As I said, the phone is can open and I can use it without problems. Looking forward to your help, thank you.
Click to expand...
Click to collapse
You need to read the instructions before you flash anything. PE A12 is encrypted by default and because TWRP can't handle the decryption of A12 ROMs, PE replacing the TWRP with PE Recovery, so to be able to get OTA updates. This is a workaround until TWRP fix the decryption issue.
To flash another ROM, take backup of the files you want from your Internal Storage, flash TWRP via ADB, wipe everything and format data. Then connect your device to PC and transfer the ROM and the files you want to flash into your Internal Storage and proceed with flashing.

Categories

Resources