I want do clean install so I evrything wipe expect user data. And there problems started. I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
I tried full wipe data - don't work. I was looking in the forum Oneplus any tutorial didin't work.
I tried this tutorial https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094 to remove warning. It works but after update from 4.0.2 to 4.1.6 warning screen again came back. It started after updating 4.1.6 to 4.1.7.
If you can slowe this problem I will be grateful. And i sorry for my engilsh
Wronko said:
I want do clean install so I evrything wipe expect user data.
Click to expand...
Click to collapse
If you want a "clean" install, user data is the most important thing to wipe; as it is the mostly likely thing to cause problem (on a new ROM, etc.).
Not related to the other issues you mentioned. But important to note, anyway.
Wronko said:
I haven't installed twrp, this warning shows up and i can't root device on 4.0.2 and 4.1.6. Aslo i can't install roms by sideload (?)
Click to expand...
Click to collapse
I'm confused. If you haven't installed TWRP, how you are trying to root? You need TWRP, in order to root.
Also, sideload can be more problematic than just flashing a ROM in TWRP. My suggestion, would be to stop messing around, and just flash TWRP.
* I wanted to write that After installing update 4.1.6 as well as on the factory as a TWRP warning appears.
*On TWRP can't root device, TWRP think the su ZIP archives od broken.
*And TWRP by bluetooth Spark can't decrypt device (my old password od bot working )
Device works fine by In addition to the aforementioned problems
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
ilyr73 said:
Hi,
As I have to send back my 3T for RMA, I spendt almost two nights with reading lots of guides about how to remove that red warning. The usual methods (flashing 4.0.2 FW and trying "dm_verity_disable/enable" with fastboot or reboot with "enforce_dm_verity", etc..) did not work at all. I ended up by this way:
- With 4.1.6 ROM flash TWRP (boot into bootloader, "fastboot flash recovery <filename>"
- In bootloader "fastboot format userdata" (this will remove encryption)
- Reboot to recovery (don't let the OS boot, otherwise you can start again)
- Flash SuperSU 2.79 (don't ask why, I guess this is needed for the encryption removal as well)
- Reboot to OS, check that encrytion is removed (in security settings, at the bottom you should see "Encrypt phone" instead of "Phone encrypted")
- Reboot recovery, flash OOS 3.5.4
- Reboot to OS, now the red warning should be removed
- Encrypt your phone (optional, if you like that way)
- Download 4.1.6 OOS image on the phone and use System update in the settings with local update to get back to 4.1.6
You should have 4.1.6 now without the red warning. If you want to get rid of the orange warning as well, you can flash the stock recovery and lock the bootloader back.
After that my phone was like an original one... With leaving some of these steps out, I always got failed..
I wrote this by memory (performed that yesterday), so it's possible I forgot something, but feel free to write a PM and I try to help. Of course the process will wipe all your data, so backup everything you need...
Click to expand...
Click to collapse
Can you link for your SuperSU zip and TWRP?
Wronko said:
Can you link for your SuperSU zip and TWRP?
Click to expand...
Click to collapse
TWRP for Oneplus 3T
SuperSU 2.79 for Oneplus 3T
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Wronko said:
After flashing su zip I want to check if I have encrypted phone and boot frozen.
So I go to recovery and install 4.1.6 rom and i get information "Error opening: '/data/system/ndebugsocet' no such file or directory"
Again something went wrong
Edit: Somehow I just install 4.0.2 (again bootloop), and stock recovery (i booted to recovery 2 times and on second try recovery ask me for password(?) so i wiped device). Everything was fine expect dm verity. At this point I give up. So having everything stock i just use ota (4.0.2>4.1.6) and this was probobly the key for success.
In the evening I will try root my device and see if everything is good.
Click to expand...
Click to collapse
Have you flashed TWRP and 3.5.4 first? Have you used bootloader with "fastboot format userdata" before flashing supersu (remembering that after this, normal boot should not start before supersu is flashed)?
Also I am not sure if flashing 3.5.4 image will update the firmware as well, but for safety, you might try to flash that as well: Oneplus 3T Firmware collection
I didn't flash 3.5.4 at all, just 4.0.2. I used "fastboot format userdata" in bootloader. And then there was a problem (boot loop.). And after that i booted into recovery(I had then stock) asked me for password )At this point I did not have any) so I wiped my device again (recovery suggest it). The device turned on normally, but still i had dm verity. Finally I updated by OTA to 4.1.6 and dm verity screen was gone.
At this point I install TWRP and rooted, without any problem.
So i think fix for this situation was going back to full stock and use OTA. (Again sorry for my English, I trying my best)
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
dev-DaT said:
thanks, i always thought that a wipe was sufficient, or at least equal to a format... anyways will report back later when i have time to try it. lets hope it works because i can't handle this chinese rom
Click to expand...
Click to collapse
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Robbo.5000 said:
The format is needed to temporarily remove encryption
I've just remembered that I missed an important step. Call it step 1.5
If you going to flash immediately after flashing official MIUI you must boot into MIUI once before doing anything else. You don't need to go through the set-up, you can boot immediately into fastboot after you get to the initial set-up page. The first boot finalises the install and is needed before you flash over the top of it. That may be the cause of your issue if you had missed this before.
Click to expand...
Click to collapse
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... now iam stuck again on fastboot screen because i wiped + formatted everything.
Edit:
When i want to flash recovery it says "OKAY" but it is unable to boot:
Sending 'recovery' (65536 KB) OKAY [ 1.562s]
Writing 'recovery' OKAY [ 0.333s]
Finished. Total time: 1.989s
Sending 'boot.img' (65536 KB) OKAY [ 1.547s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
dev-DaT said:
Ok so i flashed TWRP again, rebooted to stock rom and then rebooted into recovery, but the stock recovery is still there.
When i flash TWRP and reboot into recovery immediately i can enter TWRP, but if i reboot the phone to MIUI and then reboot again, TWRP is gone again...
It seems like TWRP does not persist... If i wipe all data trough TWRP and then reboot, i don't have OS but i do reboot back into TWRP, because well, there is nothing else...
Click to expand...
Click to collapse
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Robbo.5000 said:
This is normal, MIUI will restore stock recovery of the recovery partition changes. In order to persist TWRP you need to either install Magisk, disable dm-verity or install a custom ROM.
If you are going to flash a custom ROM, then you should do so immediately after flashing TWRP.
After formatting data, TWRP has an issue seeing the data partition, so go to the reboot menu in TWRP and select to reboot to recovery.
Then you can immediately install the ROM of choice. You cannot boot back into system as you'll lose TWRP.
Click to expand...
Click to collapse
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
dev-DaT said:
Ok, it appears that everytime i wipe system, i am not able to boot anymore into TWRP... Am i supposed to wipe System? or only wipe data & format data
Click to expand...
Click to collapse
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Robbo.5000 said:
There is no need to wipe system. You only need to wipe cache and dalvik and format data. (I choose to factory reset because it's easier in TWRP, but you could do advanced wipe and select cache and dalvik, then format data. Follow the steps exactly, but include my later step 1.5
I've just followed this myself today, as I've moved from LOS to the latest unofficial Havoc build.
In theory you could start by booting to fastboot and flashing TWRP again, then follow the steps from that point. You probably don't need to install MIUI.
Click to expand...
Click to collapse
Ok thanks a lot! So no need to wipe system partition after stock rom install. just wipe cache/dalvik/data, got it.
Most ROM install guides tell you to wipe /system when coming from stock rom. I guess this requirement has changed? or depends on what ROM you're coming from?
Use can use my guide
https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
it has how to flash roms, and fastboot fix. (which tells why the Recovery isn't staying)
Robbo.5000 said:
This works for me every time.
1 Flash the latest fastboot ROM.
2 Flash TWRP (same one you used)
3 Boot into TWRP (use the vol+ button when booting)
4 In format menu swipe to factory reset, then format data (VERY IMPORTANT this must be FORMAT not just wipe)
5 In reboot menu boot into recovery, this ensures TWRP correctly accesses the newly formatted data partition.
6 Copy over the ROM (and GApps, if needed and/or Magisk)
7 Flash the ROM, (then GApps if needed)
8 Boot into system and do the initial setup
9 If installing Magisk, boot back to TWRP and install Magisk.
There is no need to wipe anything else. There is no need to wipe anything again after installing. There is no need to disable encryption or dm-verity.
Click to expand...
Click to collapse
I need help... The reason why I'm flashing custom rom is, when the latest update came MIUI 12.5 android 11, all sensors of my phone stopped working like (Gyroscope, accelerometer, proximity sensor) I tied to flash the rom by fastboot method but still the problem persists. because of that I unlocked bootloader and flashed twrp. After flashing custom rom when I tried to boot it, it stuck on booting screen and when I tried to reboot into recovey it is showing fastboot mode. I'm unable to boot into custom rom.
dev-DaT said:
Hi all,
I was on xiaomi.eu MIUI 11 ROM for some time, but wanted to switch to either Evolution or Syberia ROM.
I did a complete wipe and installed evolution os trough twrp... but i forgot to remove encryption so i bricked my device...
So then, I flashed the latest stock rom (11.05)with Xiaomi flash tool, but then i was stuck with the chinese ROM so...
1. I went back to bootloader and flashed mauronofrio's TWRP recovery .
2. completely wiped phone; Cache,System,Data,Internal storage
3. copied Evolution OS 4.1 to my phone
4. installed zip trough TWRP, all successfull
5. but then when rebooting, TWRP says:"No OS installed, do you wish to continue"
6. i tried other ROMs like xiaomi.eu and syberia, but these would either give me the same problem, or just bootloop until iam back in the fastboot screen...
Anyone any idea what iam doing wrong?
Click to expand...
Click to collapse
Bro I have one doubt, I installed pixel os successfully then I roll back into stock os(miui) with locking bootloader, the. Again I unlock bootloader successfully, but the problem is I am unable to install os, i tried wipe data, catch. But the stock rom was not removed. What can I do?
Using orange fox in resmi note 10 pro
Hello everyone, this thread is a guide on how to enable encryption on ROMs that have it disabled.
ROMs that have encryption disabled, usually do it because TWRP is not fully working, or they want to make switching ROMs an easier task.
This zip was created for, and only tested on Official CrDroid on Oneplus 7 Pro (guacamole), developed by Gabriel Lup.
This patch might work for other ROMs, but support is NOT guaranteed.
Before we start, a disclaimer
I am not responsible for any data loss that occurs because steps were not followed correctly.
Speaking of data loss, you will NEED to backup your data before you start, because you will be completely formatting your device in the process.
Installation steps:
Download the ROM and flash it in TWRP or fastboot
After ROM is finished installing, reboot to recovery, so that you use the slot you installed your ROM to. If you didn't flash TWRP after installing the ROM, then reboot to fastboot and boot TWRP.
After booting TWRP, and active slot having the ROM installed, flash the enable_encryption.zip
Now go to Wipe > Format data > Type yes.
Now reboot to system, and you will be encrypted. You can check by going into Settings > Security > Encryption and credentials, or you can boot TWRP and check for yourself, after setting a password of course.
Note: Flash Magisk, ONLY after your first boot, and after you have confirmed you're encrypted. Flashing most of the other stuff before first boot, like gapps, should be fine.
Upgrade steps:Unfortunately, upgrading ROM via OTA is out of the question, so you will need to update via TWRP or fastboot.
Theoretically it can be done because the updated partition is not booted, and there are apps that can flash zip files while system is booted, but I won't be trying it soon, pure and simply because some users lose root after taking an OTA, because of Magisk's addon.d survival script, and without root, modifying partitions is impossible.
There are some workarounds for this problem as well but I won't get into that.
After downloading the zip file of your ROM, and enable_encryption.zip, boot to TWRP.
Flash the update for the ROM.
Reboot to TWRP, or go to fastboot and boot it again.
Flash enable_encryption.zip, magisk if you want it, and reboot system. [NOTE: if your ROM maintainer needs you to flash anything after an update, you can do that as well after flashing this zip.]
You should be fine, and prompted for a password.
Issues that might occur:The first issue that everyone might point out is
What if I forget to flash the zip after an update, or if I take an OTA?
This is an easy fix, as long as you don't panic. If you boot the ROM without flashing the enable encryption zip, instead of "Enter your password", you will be greeted with "Encryption unsuccessful, to resume using your phone, you will need to factory reset" with a button that says "Erase all data".
DO NOT ERASE ALL DATA, THIS CAN BE EASILY FIXED.
Just go to TWRP, and flash the zip to enable encryption, then reboot, you should be able to enter your password and continue using your device.
Another one could be
What if TWRP currently doesn't support decryption?
Yeah, this happens quite a lot with guacamole and Android 11. Oneplus loves changing how encryption works whenever TWRP maintainer makes it work.
This doesn't matter that much, you can sideload both ROM and this zip, regardless of if TWRP can actually read your data or not.
And finally
Installation of the zip is failing, why?
Well, there are 3 reasons if it ever fails, first one you could solve by redownloading it, or transferring it to device/sideloading again.
The second one, could be that the ROM maintainer packaged the ROM with 100% reserved blocks in the vendor.img, thus disabling writes. I personally don't think this will ever happen on our device, but it could happen.
The third one could be solved by trying out another TWRP.
This zip uses the default encryption method that is used by stock ROM, and that is fileencryption=ice, just a thing to note when choosing to flash this.
Because of this, this zip will not work if a ROM used FBEV2, and then was disabled by the maintainer, this only enables the default FBE we have on our device.
I can't get encryption working with latest crDroid build (7.9 from August 7th). I'm getting ERROR 1 after flashing enable_encryption.zip.
I tried with both regular and FBEv2 TWRP from Nebrassy, same error. If I try to flash enable_encryption.zip a second time, it doesn't return any error but after formatting data and rebooting to system, the phone reboots to TWRP.
Any idea?
Toutatis_ said:
I can't get encryption working with latest crDroid build (7.9 from August 7th). I'm getting ERROR 1 after flashing enable_encryption.zip.
I tried with both regular and FBEv2 TWRP from Nebrassy, same error. If I try to flash enable_encryption.zip a second time, it doesn't return any error but after formatting data and rebooting to system, the phone reboots to TWRP.
Any idea?
Click to expand...
Click to collapse
Strange, try and get me a recovery log by copying /tmp/recovery.log to somewhere accessible after you encounter the error.
I get no problems flashing it. Try using Nebrassy's latest TWRP, I used that one.
Xenos7 said:
Strange, try and get me a recovery log by copying /tmp/recovery.log to somewhere accessible after you encounter the error.
I get no problems flashing it. Try using Nebrassy's latest TWRP, I used that one.
View attachment 5380447
Click to expand...
Click to collapse
Sorry, I ended up flashing another ROM as I don't want to be unencrypted. I might try again later and I'll make sure to get a log this time if still getting the error. Thank you!
Hello there,
I, too, have a problem with flashing CrDroid 7 with encryption. For context, I come from CrDroid 6, which I didn't want to leave unless we can encrypt CrDroid 7.
What I did :
-> MSM Tool in order to fully reset my phone and cleanly install OOS 10 and update to OOS 11 (only way actually, since I had a pesky error related to TWRP being unable to decrypt FBE, which made it kinda impossible to do anything)
-> Unlock bootloader
-> Boot into Nebrassys's TWRP and advance -> flash
-> Installed CrDroid 7.9 (from August 7th) on slot A
-> Switched Slot to Slot A and rebooted to recovery
-> Here, I didn't really got why, but I booted into stock recovery, so I ended up in fastboot to flash Nebrassy's TWRP and advance -> flash it again
From here, I really didn't get what happened or why.
-> Booted into TWRP to find that it can't access /data/media/TWRP/somethingElse
-> Thought that it wasn't normal since I was supposed to flash tyour zip at this point, but since I couldn't access Internal Storage neither from my phone or computer, I decided to format /data with imputing 'yes' in order to "reset" encryption keys and set it available for current TWRP.
-> Reboot to recovery to be able to use /data again
-> Ended up with a "E : Unable to decrypt FBE device", which really makes Internal Storage unavailable. From here, I just had to MSM Tool back too OOS 11 like in first step in order to get a usable phone once again.
I don't really get what I did wrong, so if you have any input, I'm willing to learn :/ Thanks in advance !
Aurion13 said:
Hello there,
I, too, have a problem with flashing CrDroid 7 with encryption. For context, I come from CrDroid 6, which I didn't want to leave unless we can encrypt CrDroid 7.
What I did :
-> MSM Tool in order to fully reset my phone and cleanly install OOS 10 and update to OOS 11 (only way actually, since I had a pesky error related to TWRP being unable to decrypt FBE, which made it kinda impossible to do anything)
-> Unlock bootloader
-> Boot into Nebrassys's TWRP and advance -> flash
-> Installed CrDroid 7.9 (from August 7th) on slot A
-> Switched Slot to Slot A and rebooted to recovery
-> Here, I didn't really got why, but I booted into stock recovery, so I ended up in fastboot to flash Nebrassy's TWRP and advance -> flash it again
Click to expand...
Click to collapse
You booted back into stock recovery because when you flash crDroid, it flashes stock lineage recovery.
Aurion13 said:
From here, I really didn't get what happened or why.
-> Booted into TWRP to find that it can't access /data/media/TWRP/somethingElse
-> Thought that it wasn't normal since I was supposed to flash tyour zip at this point, but since I couldn't access Internal Storage neither from my phone or computer, I decided to format /data with imputing 'yes' in order to "reset" encryption keys and set it available for current TWRP.
-> Reboot to recovery to be able to use /data again
-> Ended up with a "E : Unable to decrypt FBE device", which really makes Internal Storage unavailable. From here, I just had to MSM Tool back too OOS 11 like in first step in order to get a usable phone once again.
I don't really get what I did wrong, so if you have any input, I'm willing to learn :/ Thanks in advance !
Click to expand...
Click to collapse
You should consider trying to sideload the enable encryption zip rather than relying on internal storage. After you side load you need to factory reset and then boot to system.
Another thing you can try is to boot crDroid unencrypted, and then reboot to recovery, flash enable encryption zip, then factory reset and reboot to system.
Thanks for your reply !
gruntparty said:
You booted back into stock recovery because when you flash crDroid, it flashes stock lineage recovery.
Click to expand...
Click to collapse
Yeaaaaaaah, it was obvious, but I missed this so hard. I totally forgot that you had to flash back TWRP when you first flash it. Thanks !
gruntparty said:
You should consider trying to sideload the enable encryption zip rather than relying on internal storage. After you side load you need to factory reset and then boot to system.
Another thing you can try is to boot crDroid unencrypted, and then reboot to recovery, flash enable encryption zip, then factory reset and reboot to system.
Click to expand...
Click to collapse
I'm not used to use sideloading, so I tried on your advice. I didn't managed to make the installation work sadly, I don't really know why, and tbh, I can't really lose time on evenings anymore. I'll try again this week-end. I'll update at this moment if I succed (or not) and with a recovery.log. But when I installed CrDroid with sideload, TWRP kept telling me that no OS was installed, with or whitout changing slot. I still didn't managed to patch the enable_encryption.zip, I got a "error: 1" which don't really talks a lot to me. So... More to come soon I guess.
Anyway, thanks for the help, and thanks for providing the zip too, it was just what I needed to hop on CrDroid 7.
Hello again,
Little update : I did it
I guess being tired didn't really served me well, and I surely did some strange things when flashing the rom since I managed to do it just a few minutes ago.
Regarding the enable_encryption.zip, I also encountered the "Updater process ended with ERROR: 1". I went to check the logs and there was this :
Code:
file size 2093, block size 65536
Installing zip file '/sideload/package.zip'
unknown fuse request opcode 2016
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
mount: '/vendor' not in fstab
sed: /vendor/etc/fstab.qcom: No such file or directory
umount: /vendor: Invalid argument
Updater process ended with ERROR: 1
I thought the "mount: '/vendor' not in fstab" strange, so I tried to mount Vendor partition, reflashed the zip, and it worked. I just checked in settings and it says I'm encrypted, I rebooted in TWRP and it asked me for my password.
I think that this would need to be added in first post @Xenos7 and it will also probably fix the issue of @Toutatis_
Again, thanks a lot for proving the zip and for the support guys !
i installed latest update of CrDroid and followed the instruction of upgrading steps but the phone has gone to bootloop. Any solution for this?
Xenos7 said:
Hello everyone, this thread is a guide on how to enable encryption on ROMs that have it disabled.
ROMs that have encryption disabled, usually do it because TWRP is not fully working, or they want to make switching ROMs an easier task.
This zip was created for, and only tested on Official CrDroid on Oneplus 7 Pro (guacamole), developed by Gabriel Lup.
This patch might work for other ROMs, but support is NOT guaranteed.
Before we start, a disclaimer
I am not responsible for any data loss that occurs because steps were not followed correctly.
Speaking of data loss, you will NEED to backup your data before you start, because you will be completely formatting your device in the process.
Installation steps:
Download the ROM and flash it in TWRP or fastboot
After ROM is finished installing, reboot to recovery, so that you use the slot you installed your ROM to. If you didn't flash TWRP after installing the ROM, then reboot to fastboot and boot TWRP.
After booting TWRP, and active slot having the ROM installed, flash the enable_encryption.zip
Now go to Wipe > Format data > Type yes.
Now reboot to system, and you will be encrypted. You can check by going into Settings > Security > Encryption and credentials, or you can boot TWRP and check for yourself, after setting a password of course.
Note: Flash Magisk, ONLY after your first boot, and after you have confirmed you're encrypted. Flashing most of the other stuff before first boot, like gapps, should be fine.
Upgrade steps:Unfortunately, upgrading ROM via OTA is out of the question, so you will need to update via TWRP or fastboot.
Theoretically it can be done because the updated partition is not booted, and there are apps that can flash zip files while system is booted, but I won't be trying it soon, pure and simply because some users lose root after taking an OTA, because of Magisk's addon.d survival script, and without root, modifying partitions is impossible.
There are some workarounds for this problem as well but I won't get into that.
After downloading the zip file of your ROM, and enable_encryption.zip, boot to TWRP.
Flash the update for the ROM.
Reboot to TWRP, or go to fastboot and boot it again.
Flash enable_encryption.zip, magisk if you want it, and reboot system. [NOTE: if your ROM maintainer needs you to flash anything after an update, you can do that as well after flashing this zip.]
You should be fine, and prompted for a password.
Issues that might occur:The first issue that everyone might point out is
What if I forget to flash the zip after an update, or if I take an OTA?
This is an easy fix, as long as you don't panic. If you boot the ROM without flashing the enable encryption zip, instead of "Enter your password", you will be greeted with "Encryption unsuccessful, to resume using your phone, you will need to factory reset" with a button that says "Erase all data".
DO NOT ERASE ALL DATA, THIS CAN BE EASILY FIXED.
Just go to TWRP, and flash the zip to enable encryption, then reboot, you should be able to enter your password and continue using your device.
Another one could be
What if TWRP currently doesn't support decryption?
Yeah, this happens quite a lot with guacamole and Android 11. Oneplus loves changing how encryption works whenever TWRP maintainer makes it work.
This doesn't matter that much, you can sideload both ROM and this zip, regardless of if TWRP can actually read your data or not.
And finally
Installation of the zip is failing, why?
Well, there are 3 reasons if it ever fails, first one you could solve by redownloading it, or transferring it to device/sideloading again.
The second one, could be that the ROM maintainer packaged the ROM with 100% reserved blocks in the vendor.img, thus disabling writes. I personally don't think this will ever happen on our device, but it could happen.
The third one could be solved by trying out another TWRP.
This zip uses the default encryption method that is used by stock ROM, and that is fileencryption=ice, just a thing to note when choosing to flash this.
Because of this, this zip will not work if a ROM used FBEV2, and then was disabled by the maintainer, this only enables the default FBE we have on our device.
Click to expand...
Click to collapse
Hi! Done. Followed all steps and crdroid is now encrypted. But! Very strange behavior which I tested several times. After having OS encrypted I decided to go again to recovery, now from crdroid power/restart menu. But recovery didn't load. Instead, I had a recovery (TWRP Nebrassy) logo flicking. I hard-switched to fastboot, then fastboot boot twrp.img, and entered TWRP menu (temporary TWRP). In there I was trying to flash TWRP on permanent basis again but it failed with an error about mounting data. Format data didn't help. So, I stayed on temporary TWRP and after reboot to System, surprisingly successfully entered my crdroid. The same happens (checked) if I would reboot to Recovery - instead of Recovery I would enter crdroid. The only explanation I see is that encryption (done with this zip) blocks permanently installed TWRP from starting. In case of temporary TWRP it's just being disappeared after reboot and I can enter the system whatever option I choose in temporary TWRP: system or recovery. It would be OK but the sad thing I need the both encryption and recovery. Any ideas?
P.S. I tried also Orangefox recovery - the same story : logo flicking after the try to restart from encrypted crdroid to recovery.
Yagikable said:
Hi! Done. Followed all steps and crdroid is now encrypted. But! Very strange behavior which I tested several times. After having OS encrypted I decided to go again to recovery, now from crdroid power/restart menu. But recovery didn't load. Instead, I had a recovery (TWRP Nebrassy) logo flicking. I hard-switched to fastboot, then fastboot boot twrp.img, and entered TWRP menu (temporary TWRP). In there I was trying to flash TWRP on permanent basis again but it failed with an error about mounting data. Format data didn't help. So, I stayed on temporary TWRP and after reboot to System, surprisingly successfully entered my crdroid. The same happens (checked) if I would reboot to Recovery - instead of Recovery I would enter crdroid. The only explanation I see is that encryption (done with this zip) blocks permanently installed TWRP from starting. In case of temporary TWRP it's just being disappeared after reboot and I can enter the system whatever option I choose in temporary TWRP: system or recovery. It would be OK but the sad thing I need the both encryption and recovery. Any ideas?
P.S. I tried also Orangefox recovery - the same story : logo flicking after the try to restart from encrypted crdroid to recovery.
Click to expand...
Click to collapse
Forgot to add: Format data failed with "couldn't format encrypted data"
Yagikable said:
Hi! Done. Followed all steps and crdroid is now encrypted. But! Very strange behavior which I tested several times. After having OS encrypted I decided to go again to recovery, now from crdroid power/restart menu. But recovery didn't load. Instead, I had a recovery (TWRP Nebrassy) logo flicking. I hard-switched to fastboot, then fastboot boot twrp.img, and entered TWRP menu (temporary TWRP). In there I was trying to flash TWRP on permanent basis again but it failed with an error about mounting data. Format data didn't help. So, I stayed on temporary TWRP and after reboot to System, surprisingly successfully entered my crdroid. The same happens (checked) if I would reboot to Recovery - instead of Recovery I would enter crdroid. The only explanation I see is that encryption (done with this zip) blocks permanently installed TWRP from starting. In case of temporary TWRP it's just being disappeared after reboot and I can enter the system whatever option I choose in temporary TWRP: system or recovery. It would be OK but the sad thing I need the both encryption and recovery. Any ideas?
P.S. I tried also Orangefox recovery - the same story : logo flicking after the try to restart from encrypted crdroid to recovery.
Click to expand...
Click to collapse
I never install TWRP, so I can't really say about that, but I'm sure the zip shouldn't impact the recovery installing/booting.
Try downloading the latest version of Nebraccy TWRP, the August one. That one should work if OnePlus didn't change something with encryption again.
This zip doesn't even touch the boot partition, it only edits 2 lines in vendor partition, which would never make TWRP unable to install.
However, last time I tried, in June and decrypted, TWRP wouldn't install at all anyways.
Xenos7 said:
I never install TWRP, so I can't really say about that, but I'm sure the zip shouldn't impact the recovery installing/booting.
Try downloading the latest version of Nebraccy TWRP, the August one. That one should work if OnePlus didn't change something with encryption again.
This zip doesn't even touch the boot partition, it only edits 2 lines in vendor partition, which would never make TWRP unable to install.
However, last time I tried, in June and decrypted, TWRP wouldn't install at all anyways.
Click to expand...
Click to collapse
Thanks. When next update for crdroid comes, I'll try again from the scratch. Meanwhile, the issue was magically solved. I was sick and tired with this flicking recovery and decided to flash lineage recovery from the command line. It was a surprise when instead of seeing lineage after reboot I saw my Nebrassy TWRP fully loaded and never flicking since then. Crdroid has also successfully run encrypted. I have no explanation for that. Maybe it has something to do with a/b slots but I'm sure I've been choosing the right slots all the time.
Use this to enable FBEv2 instead of sdcardfs. Use the instructions from the OP.
Mount vendor in TWRP before flashing. Also, flash an FBEv2 kernel.
EDIT: Don't complain to the dev or me if your data is gone or your device blows up.
darkflicker said:
Use this to enable FBEv2 instead of sdcardfs. Use the instructions from the OP.
Mount vendor in TWRP before flashing. Also, flash an FBEv2 kernel.
Click to expand...
Click to collapse
Why would you purposely try to break stuff?
Technically, that IS possible, but, just, why?
You receive no visible benefits, and you could lose all your data once major Android version is updated...
Not to mention users will complain to dev when random bugs happen because they use some out of the nowhere kernel.
As for sdcardfs or fuse?
I can bet that people CAN'T know the difference between them, looking at the fact everyone asks if the ROM is sdcardfs or not.
Fact is, using this method on a ROM that's supposed to use regular FBE, is possible, but NOT recommended.
Putting all your data on the line because of theoretical performance bumps is a plainly stupid idea if you ask me.
Either use a FBEV2 ROM, or don't, although people make a big fuss about it being sdcardfs or not, FBEV2 or not.
Those things should NEVER be a deciding factor, because every non developer user, really can't tell the difference.
Xenos7 said:
Why would you purposely try to break stuff?
Technically, that IS possible, but, just, why?
You receive no visible benefits, and you could lose all your data once major Android version is updated...
Not to mention users will complain to dev when random bugs happen because they use some out of the nowhere kernel.
As for sdcardfs or fuse?
I can bet that people CAN'T know the difference between them, looking at the fact everyone asks if the ROM is sdcardfs or not.
Fact is, using this method on a ROM that's supposed to use regular FBE, is possible, but NOT recommended.
Putting all your data on the line because of theoretical performance bumps is a plainly stupid idea if you ask me.
Either use a FBEV2 ROM, or don't, although people make a big fuss about it being sdcardfs or not, FBEV2 or not.
Those things should NEVER be a deciding factor, because every non developer user, really can't tell the difference.
Click to expand...
Click to collapse
You are also forcefully trying to enable encryption on a decrypted and unsupported ROM. The chances of breakage are similar for both. I am just providing the users a choice. If anything breaks, nobody is responsible but them.
darkflicker said:
You are also forcefully trying to enable encryption on a decrypted and unsupported ROM. The chances of breakage are similar for both. I am just providing the users a choice. If anything breaks, nobody is responsible but them.
Click to expand...
Click to collapse
The ROM fully supports encryption on it's kernel, dev is just not using it to keep TWRP support, this was before A11 TWRP got released. I'm assuming he doesn't want users to clean flash just because of encryption.
This zip just reverts the commit made to fstab to disable encryption, and you're still using the kernel developer intended.
But sure, if someone breaks their device, it's their own fault.
Fellas yall going backwards with all this. Encryption is the devil.
Updated the zip to include checks to unmount vendor if someone mounted it manually, so that it shouldn't get errors for that now.
The zip can be found in OP.
Xenos7 said:
Hello everyone, this thread is a guide on how to enable encryption on ROMs that have it disabled.
ROMs that have encryption disabled, usually do it because TWRP is not fully working, or they want to make switching ROMs an easier task.
This zip was created for, and only tested on Official CrDroid on Oneplus 7 Pro (guacamole), developed by Gabriel Lup.
This patch might work for other ROMs, but support is NOT guaranteed.
Before we start, a disclaimer
I am not responsible for any data loss that occurs because steps were not followed correctly.
Speaking of data loss, you will NEED to backup your data before you start, because you will be completely formatting your device in the process.
Installation steps:
Download the ROM and flash it in TWRP or fastboot
After ROM is finished installing, reboot to recovery, so that you use the slot you installed your ROM to. If you didn't flash TWRP after installing the ROM, then reboot to fastboot and boot TWRP.
After booting TWRP, and active slot having the ROM installed, flash the enable_encryption.zip
Now go to Wipe > Format data > Type yes.
Now reboot to system, and you will be encrypted. You can check by going into Settings > Security > Encryption and credentials, or you can boot TWRP and check for yourself, after setting a password of course.
Note: Flash Magisk, ONLY after your first boot, and after you have confirmed you're encrypted. Flashing most of the other stuff before first boot, like gapps, should be fine.
Upgrade steps:Unfortunately, upgrading ROM via OTA is out of the question, so you will need to update via TWRP or fastboot.
Theoretically it can be done because the updated partition is not booted, and there are apps that can flash zip files while system is booted, but I won't be trying it soon, pure and simply because some users lose root after taking an OTA, because of Magisk's addon.d survival script, and without root, modifying partitions is impossible.
There are some workarounds for this problem as well but I won't get into that.
After downloading the zip file of your ROM, and enable_encryption.zip, boot to TWRP.
Flash the update for the ROM.
Reboot to TWRP, or go to fastboot and boot it again.
Flash enable_encryption.zip, magisk if you want it, and reboot system. [NOTE: if your ROM maintainer needs you to flash anything after an update, you can do that as well after flashing this zip.]
You should be fine, and prompted for a password.
Issues that might occur:The first issue that everyone might point out is
What if I forget to flash the zip after an update, or if I take an OTA?
This is an easy fix, as long as you don't panic. If you boot the ROM without flashing the enable encryption zip, instead of "Enter your password", you will be greeted with "Encryption unsuccessful, to resume using your phone, you will need to factory reset" with a button that says "Erase all data".
DO NOT ERASE ALL DATA, THIS CAN BE EASILY FIXED.
Just go to TWRP, and flash the zip to enable encryption, then reboot, you should be able to enter your password and continue using your device.
Another one could be
What if TWRP currently doesn't support decryption?
Yeah, this happens quite a lot with guacamole and Android 11. Oneplus loves changing how encryption works whenever TWRP maintainer makes it work.
This doesn't matter that much, you can sideload both ROM and this zip, regardless of if TWRP can actually read your data or not.
And finally
Installation of the zip is failing, why?
Well, there are 3 reasons if it ever fails, first one you could solve by redownloading it, or transferring it to device/sideloading again.
The second one, could be that the ROM maintainer packaged the ROM with 100% reserved blocks in the vendor.img, thus disabling writes. I personally don't think this will ever happen on our device, but it could happen.
The third one could be solved by trying out another TWRP.
This zip uses the default encryption method that is used by stock ROM, and that is fileencryption=ice, just a thing to note when choosing to flash this.
Because of this, this zip will not work if a ROM used FBEV2, and then was disabled by the maintainer, this only enables the default FBE we have on our device.
Click to expand...
Click to collapse
Is this enable_encryption.zip only works for oneplus 7 pro ?? If so then can you please provide the file that works for Mi A2.