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).
Related
I have been struggling to encrypt MI 8 as without encryption, I feel like I am walking naked
After lots of trial and error, finally got it working. Here are the steps:
Prerequisites: Flash TWRP (TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150) by @gulp79 - https://goo.gl/scMQwd
1. Copy the following files to the phone:
a. Vendor/firmware from @infrag - https://drive.google.com/open?id=1BJKthOJrWaWevaxus7rYkJNc95icIOsD
b. Copy Havoc (Dipper Update 25-11-2018) by @ZeNiXxX + Gapps to the phone.
c. Titanium Backup all the user apps and copy the backup to your PC. You will have to format data and you will lose everything on the phone.
2. Reboot to TWRP.
3. Flash vendor/firmware + Havoc + Gapps.
4. Wipe - Format Data (where you have to type "yes"). This will wipe everything from your /data partition, including /sdcard.
5. Reboot to System.
6. Setup the phone and add fingerprint/PIN (important).
7. Restore the user apps from Titanium Backup by copying the backup from the PC.
8. If you need Magisk, copy it to /sdcard and reboot to TWRP and flash it. When you boot to TWRP, you will be prompted to enter PIN to decrypt data.
Voila!
Phone is encrypted and you can sleep happy.
PS: Big thanks to @ZeNiXxX (for an awesome and feature rich Havoc ROM), @gulp79 (for converting the latest TWRP to English), @infrag (for providing the flashable vendor/firmware), @milouk (default kernel in Havoc), and OpenGAPPS team.
What exactly does it do?
By.TRabZonLu™ said:
What exactly does it do?
Click to expand...
Click to collapse
It encrypts your phone. If you ever lose a phone, no one can access your data.
Without encryption, if you give me a phone which has a PIN or Pattern setup with/without fingerprint, I can easily remove the PIN/Pattern in TWRP and boot your phone and look at all the data.
Without encryption, it's analogous to walking naked.
You should specify that it is for AOSP & LOS in title, MIUI Stock Global & China has built in System & Data encryption already. ( .EU multi ROM has only system encryption)
RainGater said:
I have been struggling to encrypt MI 8 as without encryption, I feel like I am walking naked
Snip
Click to expand...
Click to collapse
My phone is on global stable. Do I use the same steps if I want to keep my phone encrypted? Thanks a lot!
What if you want to have encryption using MIUI ROM ?
pmatthew said:
What if you want to have encryption using MIUI ROM ?
Click to expand...
Click to collapse
This thread is outdated, encryption works well now.
nfsmw_gr said:
This thread is outdated, encryption works well now.
Click to expand...
Click to collapse
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
pmatthew said:
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
Click to expand...
Click to collapse
I still can't find a way for GLOBAL ROM (latest PIE) to have DATA & SYSTEM encryption while keeping ROOT. Boot loops to recovery every time.... If anyone has this or can achieve this, please share. The closest i've been is I can get root, and have DM Verity with Optional encryption just fine -but as soon as i choose to encrypt the phone from the menu, it errors trying, then continuously boot loops.
pmatthew said:
I would not say that; yesterday I turned on the Phone encryption on xiaomi.eu stable rom (MIUI 10.2), and after that the phone booted only to Recovery. I had to format data, reinstall the ROM, and modify fstab.qcom, to have encryption...
Click to expand...
Click to collapse
Agimax said:
I still can't find a way for GLOBAL ROM (latest PIE) to have DATA & SYSTEM encryption while keeping ROOT. Boot loops to recovery every time.... If anyone has this or can achieve this, please share. The closest i've been is I can get root, and have DM Verity with Optional encryption just fine -but as soon as i choose to encrypt the phone from the menu, it errors trying, then continuously boot loops.
Click to expand...
Click to collapse
Umm, I flashed latest global myself a couple of days ago through fastboot.
I admit I didn't root the clean booted global rom, but mi-globe and xiaomi.eu variants got rooted just fine for me with Magisk V18.0.
nfsmw_gr said:
Umm, I flashed latest global myself a couple of days ago through fastboot.
I admit I didn't root the clean booted global rom, but mi-globe and xiaomi.eu variants got rooted just fine for me with Magisk V18.0.
Click to expand...
Click to collapse
Of course, Root without encryption is fine. Try running ROOT with DATA & SYSTEM encryption. That is the issue i am finding. Xiaomi.eu doesn't come with encryption out of the box for DATA. GLOBAL ROM defaults to encryption for SYSTEM & DATA on first boot. If it's not encrypted or flashing the DM-Verity/FEC remover first, running Magisk root is fine. As i stated, GLOBAL ROM with ROOT and FULL system & data encryption is where the issue lies.
Agimax said:
Of course, Root without encryption is fine. Try running ROOT with DATA & SYSTEM encryption. That is the issue i am finding. Xiaomi.eu doesn't come with encryption out of the box for DATA. GLOBAL ROM defaults to encryption for SYSTEM & DATA on first boot. If it's not encrypted or flashing the DM-Verity/FEC remover first, running Magisk root is fine. As i stated, GLOBAL ROM with ROOT and FULL system & data encryption is where the issue lies.
Click to expand...
Click to collapse
No I mean I was encrypted as well.
I'd try again just to be sure about what I said but I've finalized my LOS setup right now haha.
I'm almost 100% certain I was encrypted because I never formated data from twrp, just flashed stock, twrp, xiaomi.eu, magisk.
This shouldn't remove the encryption, and besides without the remover zip the rom enforces encryption, and I didn't flash the remover zip.
nfsmw_gr said:
No I mean I was encrypted as well.
I'd try again just to be sure about what I said but I've finalized my LOS setup right now haha.
I'm almost 100% certain I was encrypted because I never formated data from twrp, just flashed stock, twrp, xiaomi.eu, magisk.
This shouldn't remove the encryption, and besides without the remover zip the rom enforces encryption, and I didn't flash the remover zip.
Click to expand...
Click to collapse
- you said you flashed twrp, xiaomi.eu and magisk. Xiaomi.eu isn't encrypted by default without editing the values manually......Soo.... No you didn't have encryption and root in that scenario.
Agimax said:
- you said you flashed twrp, xiaomi.eu and magisk. Xiaomi.eu isn't encrypted by default without editing the values manually......Soo.... No you didn't have encryption and root in that scenario.
Click to expand...
Click to collapse
If I didn't format data after flashing xiaomi.eu the encryption has no reason to be gone.
If it had gone then the internal storage on my device would be blank. But all the files were there.
So yeah the encryption remained.
In any case believe what you will, I'm not gonna flash everything again just to prove my point.
If I need to go back to miui for any reason I'll do it and post back, otherwise give it a go yourself.
nfsmw_gr said:
If I didn't format data after flashing xiaomi.eu the encryption has no reason to be gone.
If it had gone then the internal storage on my device would be blank. But all the files were there.
So yeah the encryption remained.
In any case believe what you will, I'm not gonna flash everything again just to prove my point.
If I need to go back to miui for any reason I'll do it and post back, otherwise give it a go yourself.
Click to expand...
Click to collapse
I've tried xiaomi.eu in the past. The latest build i tried is dec 22, 2018, but the phone never encrypted. Contrary to LOS it always encrypted when i flashed it.
So, if your phone encrypted, then you need to decrypt it by entering the pattern/security when booting to recovery right?
To make sure if my phone encrypted, i boot to twrp and security pattern will appear. If its not encrypted, there will be no security pattern in twrp boot. I double checked it with connecting the phone with usb cable, An encrypted phone will always displaying random text/folder file, while not encrypted phone always display the real file.
So, i formatted data and flash xiaomi.eu (magisk etc) to see if it encrypted, its not. And i wipe everything again, i flashed LOS (etc), but it still not encrypted. So, i formatted data, and flash LOS (etc) right away, and the the phone was encrypt.
I think the fault was xiaomi.eu dec 22 build???
So, my final conclusion atm xiaomi.eu encryption is still fail.
Sent from my Mi 8 using Tapatalk
Yes MIUI ROM encryption is still fail
Just to confirm post above.
This eu rom encrypt only if you trip Fstab or you flash before an official Miui rom and encrypt it. then you can flash custom miui rom or miuirum and encrytion stay.
I don't explain why but I tested it on my old MI5.
Totally an unnecessary effort, but useful for those FBI agents. It's also hard to remove the encryption tho, I flashed a thousand times to remove the encryption and I won't mess with it again, but still an useful thread for FBI agents.
Finally figured out how to Root MIUI Global Stock AND keep DATA/Storage encryption
https://forum.xda-developers.com/showpost.php?p=78988313&postcount=4
Does this have something in relation with the bootloop when I try to flash any ROM that's different than MIUI? I'm very curious because my Mi 8 started to have bootloop problems when the Android Pie came out. Only one version of TWRP works for me, PixelExperience gives me bootloop when I flash it, xiaomi.eu works only following very specific steps (and this is the only one I've succesfully installed).
Hey guys, I'm trying to install LineageOS GSI (arm64 A/B) on my Mi A3 and seem to be having some trouble getting the GSI to actually boot successfully.
I have already done my research both on XDA and elsewhere online, yet most threads focused on the device seem to be of little to no use and/or filled with spam replies that only serve to confuse people looking into this.
A quick note regarding the aforementioned threads:
I don't mean to sound disrespectful to the community, but honestly, bashing somebody over why they'd rather install anything but your own fav piece of software is completely ridiculous.
Without further ado, my case goes as follows:
I'm starting fresh with the latest stock firmware, after having unlocked my bootloader ofc (critical too), I've successfully installed TWRP, wiped, installed the system image and yet after rebooting I'm just greeted with good ol' Fastboot, at which point I either directly flash the stock firmware and try again or wipe my data and whatnot (through TWRP, if reinstalled) and still end up with Fastboot.
Therefore, I have to ask you guys:
Has anyone previously successfully installed any GSI rom on the Mi A3?
Did you flash the system img while on stock firmware or a previously flashed custom rom (ie Pixel Experience)?
Is there any need for any special patch similar to the ones used for MIUI based Xiaomi phones?
Did you face any other issues while trying to flash a GSI?
My intention is to eventually install microG using Nanodroid.
Thanks for asking. I was trying to flash Havoc, crDroid and MSM-Xtended Android 10 GSIs but I can't boot the phone.
I have flashed lots of GSIs in the past, but this is really intriguing me, I can't boot on Mi A3. Wiping or formatting data does not solve, neither Permissiver or Disable Dm-verity zips did the job... :crying:
I successfully bootet the LineageOS GSI yesterday. I was not coming from stock though. I think this process should work assuming you already bootet to TWRP:
1. flash the GSI image to system partition using TWRP
2. flash the TWRP installer to keep your recovery
3. (not sure if needed) flash no fde patch
4. optional: flash some other stuff like Magisk and gapps
5. wipe data and dalvik
I think it rebooted to recovery on my first try but worked after flashing everything again. I probably made some mistake on my first attempt but just make sure to try again before giving up.
Also there's this tutorial but it's not at all what I did to get it working:
https://forum.xda-developers.com/mi-a3/how-to/tutorial-flash-custom-rom-mi-a3-t3977169
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
61zone said:
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
Click to expand...
Click to collapse
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
callmebutcher101 said:
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
Click to expand...
Click to collapse
Actually there is too much information to handle at once that's why i got confused lol. Thanks for the infos :good:
I'll try to do according to your info.
{
"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.
{
"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.