Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
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.