For Unlocked Bootloader Devices - Flash at your own risk. Make sure to take a complete internal memory backup before flashing.
Following is a copy-paste from OP Forums
Hey everyone,
We know everyone is excited to finally try the delicious Pie update on the OnePlus 3 and OnePlus 3T. Thanks to the feedback from our beta testers, we are getting closer to launching Android Pie on the OnePlus 3 and 3T.
Now, we would like to invite you to download and try the Community Build available here and continue to help us shaping the stable update. Anyone can try this build, but please have in mind it won’t be available via OTA, you’ll have to download and install it yourself.
Community Beta for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_075_all_1904171151_74affb85cc694452.zip
Community Beta for OnePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_075_all_1904171149_20a0443ddf734944.zip
Those who download the Community Beta build will get OTA update when the stable build is released.
Changelog
System
Updated system to Android™ 9 Pie™
Brand new UI for Android Pie
Updated Android security patch to 2019.4
Do Not Disturb mode
New Do Not Disturb mode with adjustable settings
New Gaming mode 3.0
Added text notification mode
Added notification for 3rd party calls
Phone
Deep integration with Google Duo
Camera
Integrated Google Lens mode
Instructions for updating to the Community Build
For those on the latest stable version 181206
Preconditions: Boot Loader should be locked
Steps:
Download the file from the link provided on the forum post
Move the downloaded file to internal storage root folder using the File Manager.
The device can then be updated via two methods.
First method: Local Update
Open Settings -> System update -> Click top right setting icon
Choose Local update
Click on the downloaded file and wait until the device reboots
Second Method: Recovery Update
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
For those who are on the latest Open Beta version 180712
Note: The entire data will be wiped since there will be a version transition from Open beta to the stable version. If you made a OnePlus Switch backup, be sure to make a copy of it before moving forward.
Steps:
Download the file form the link provided on the forum post
Move the downloaded file to internal storage
Device can be updated only via Recovery Update:
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
Thank you once again for all your patience and we can’t wait to get your feedback.
We are one step closer to releasing the Pie for OnePlus 3 / 3T, you can now download and try our community build right now.
Never Settle.
EDIT 1
Procedure that worked for me
So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
EDIT 2:
Community Beta 2 Released 5/6/2019
Hey everyone,
Here is the Community beta 2 for the OnePlus 3 and OnePlus 3T, the update primarily contains bug fixes:
Changelog
Bug fixes
Clock timer and stopwatch interface display is incomplete
Microphone doesn't work when earphones are plugged in
Crash issues with native message app
Community Beta 2 for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_080_all_1905061403_459f9d6e543f4a16.zip
Community Beta 2 for onePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_080_all_1905061406_f9d7f76f3a5d45da.zip
I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?
brian13th said:
I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?
Click to expand...
Click to collapse
I am currently at work. I will flash it once I am home. but make sure you take complete backup of your internal memory. It will mess up your internal data partition if you have unlocked bootloader. Don't take an unnecessary risk with your data.
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.
FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
kojakcr said:
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.
Click to expand...
Click to collapse
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?
abhibnl said:
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?
Click to expand...
Click to collapse
I am
FSadino said:
I am
Click to expand...
Click to collapse
Seems like there is no other way than to format internal memory once. I'm on stock 5.0.8 rooted and UL BL
Where I found a download link from stock recovery.
On the OnePlus page I don't found it.
After flash stock recovery I must locked bootloader
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Clean install, twrp 3.30-1, magisk, everything's fine
Thank you oneplus
On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19
What's the procedure if I'm on twrp with custom rom?
Ed_Newgate said:
What's the procedure if I'm on twrp with custom rom?
Click to expand...
Click to collapse
The procedure is always the same, the results may be different.
Factory reset
Wipe data, system, cache, art
Flash zip
Reboot
So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
Let me know if you need additional help.
would u say worth changing to this from the one3os cb rom all seems to be the same there as this?
ireaper4592 said:
would u say worth changing to this from the one3os cb rom all seems to be the same there as this?
Click to expand...
Click to collapse
I can't say for sure. I have never tested CB. But this is the latest we have and it could have some under the hood fixes. I would recommend flashing this over CB
I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...
HouseFuzzy said:
I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...
Click to expand...
Click to collapse
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright gonna give it an other try then. Flashed the Pie OOS now via TWRP at around 11.20 german time. If its not getting over the boot animation by like 12.00 german time im gonna reply again.
---------- Post added at 12:16 PM ---------- Previous post was at 11:27 AM ----------
abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright been letting it go an hour now. Still in the boot animation.
svandasek said:
On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19
Click to expand...
Click to collapse
Having similar issue, but on my side Magisk is installed, apps correctly receives the root privileges, but AdAway can't install the hosts file, it says system partition is full.
Hello.
I flash OnePlus 3T stock pie 9.0.3 to (ROM) aroma pie 9.0.4 with twrp (3.2.3.1)
My mobile got brick after then i use msmdownload tool from 1.11Gb mega.nz l then i got back my phone on Marshalls mallow but when i trying to upgrade to stock 9.0.3 pie with the twrp 3.2.3.1 successful flashed the rom and reboot to system but i can boot to system 3,4 hours still loading on red circle when stock first boot logo please help me what i do i need to upgrade stock 9.0.3 pie at least instead of custom rom now im using Miui 10 in OnePlus 3T so please guide me how i can back to upgraded os because i don't want to use custom rom
zunairkh said:
Hello.
I flash OnePlus 3T stock pie 9.0.3 to (ROM) aroma pie 9.0.4 with twrp (3.2.3.1)
My mobile got brick after then i use msmdownload tool from 1.11Gb mega.nz l then i got back my phone on Marshalls mallow but when i trying to upgrade to stock 9.0.3 pie with the twrp 3.2.3.1 successful flashed the rom and reboot to system but i can boot to system 3,4 hours still loading on red circle when stock first boot logo please help me what i do i need to upgrade stock 9.0.3 pie at least instead of custom rom now im using Miui 10 in OnePlus 3T so please guide me how i can back to upgraded os because i don't want to use custom rom
Click to expand...
Click to collapse
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...
Master_TC said:
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...
Click to expand...
Click to collapse
You should have said "use the latest", in this case 3.3.1-0 instead
Master_TC said:
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...
Click to expand...
Click to collapse
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1
Immortalis said:
You should have said "use the latest", in this case 3.3.1-0 instead
Click to expand...
Click to collapse
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1
zunairkh said:
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1
Click to expand...
Click to collapse
Yes you can.
The latest version is 3.3.1.0. Sorry i have mistyped.
i failed
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system
Master_TC said:
Yes you can.
The latest version is 3.3.1.0. Sorry i have mistyped.
Click to expand...
Click to collapse
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system
zunairkh said:
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system
Click to expand...
Click to collapse
OK you want to use the original OxygenOS 9.0.4?
Then go this way (all your data will be lost!):
1. in TWRP (3.3.1.0) delete all partitions (Dalvik, Cache, System, Data,...)
2. reboot into TWRP
3. format Data in Wipe - Format Data - type YES
4. reboot into TWRP
5. connect your phone with your computer and install full OxygenOS 9.0.4 zip (download from OP page)
6. reboot into TWRP and install magisk, if you want to keep TWRP. Else reboot into system
First boot takes 5-10 Minutes.
Thanks sir i will try and inform you if it work i will be thanks ful
Master_TC said:
OK you want to use the original OxygenOS 9.0.4?
Then go this way (all your data will be lost!):
1. in TWRP (3.3.1.0) delete all partitions (Dalvik, Cache, System, Data,...)
2. reboot into TWRP
3. format Data in Wipe - Format Data - type YES
4. reboot into TWRP
5. connect your phone with your computer and install full OxygenOS 9.0.4 zip (download from OP page)
6. reboot into TWRP and install magisk, if you want to keep TWRP. Else reboot into system
First boot takes 5-10 Minutes.
Click to expand...
Click to collapse
step 1 All partition include ( internal storage)?
Step 5 for transfer file oxygenos.zip? How to install though computer adb sideload or twrp flashing swipe
zunairkh said:
step 1 All partition include ( internal storage)?
Step 5 for transfer file oxygenos.zip? How to install though computer adb sideload or twrp flashing swipe
Click to expand...
Click to collapse
1. without internal storage (you can wipe it too, if you don't have any important data)
5. yes to transfer file or you use a sdcard. install OS in TWRP
I wiped all thing
And wiped format data and instll oxygen os 9.0.4 with magisk
Thanks ? you solve my issue
If i want to imstall aroma rom so can i do same process
?
zunairkh said:
I wiped all thing
And wiped format data and instll oxygen os 9.0.4 with magisk
Thanks you solve my issue
If i want to imstall aroma rom so can i do same process
?
Click to expand...
Click to collapse
Yes, so you can install all roms clean and without problems.
Don't forget to save your data!
Master_TC said:
Yes, so you can install all roms clean and without problems.
Don't forget to save your data!
Click to expand...
Click to collapse
Is there any method i can download miui cloud message,call history backup without install miui rom
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Unlock and flash recovery
Backup
Format Data! (It's important if you come from Miui)
Install Q Firmware + vendor
Install LineageOS followed by gapps
Reboot into system and setup device.
Reboot into recovery and flash magisk
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
I also dont know if its possible to get recovery and rom on android 10 versions.
Thanks
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Flash a custom recovery
Create a backup
Root???
Install LineageOS
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
Thanks
Click to expand...
Click to collapse
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
You could also check LOS thread: Here and here
Remember:
Chinese firmware: Widevine L3 and NFC support
Indian firmware: Widevine L1 but no NFC support
ishaqtkr said:
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
They may work as it but I was just wondering if anyone could go into more detail or if there was a better approach and from what Kollachi said there clearly is a better way that what I said.
Since I'm in stock ROM and haven't ever flashed AOSP ROM in this phone I'll just back off lol
Sent from my Redmi K20 Pro using Tapatalk
Kollachi said:
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
Click to expand...
Click to collapse
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Any of the two recoveries will work. Q firmware means Android Q. Wile data/cache dalvik that's it. Regarding firmware, there's a clear topic of Lineage OS in K20 Pro forum which is still in unofficially state
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
1. You can take what you want. Orangefox is based on TWRP.
2. Format data is needed if you come from miui. If you did it you are good to go. But it wouldn't be false to wipe system, dalvic, cache
3.https://downloads.akhilnarang.me/MIUI/raphael/ --> Take 10.4.6.0 or 10.4.8.0 (Android 10 = Q)
4. No there is no specific version.
BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
I would recommend the latest TWRP from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469/post80406191
Robbo.5000 said:
I would recommend the latest TWRP from here
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
Click to expand...
Click to collapse
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Kollachi said:
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Click to expand...
Click to collapse
Yes flashing the whole fastboot ROM does add the risk, if you forget to change the flash option, but you are guaranteed a clean slate and so less likely to have any niggling issues that nobody else has. I would bet large sums of money that many of the issues you see on here, where only one person has some problem and everyone else is fine, would be solved by fastboot flashing MIUI before installing the ROM of choice.
If you know what you're doing and know when you'll be OK with what you've got and know when it's best to start clean, then going with the vendor and firmware is easier.
But if your unsure and new to flashing on Android phones, I will always suggest go with the overkill and know you've got the clean slate to start with.
---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
Click to expand...
Click to collapse
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
You connect your phone to computer while in recovery to transfer the OS zip
Sent from my Redmi K20 Pro using Tapatalk
BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
After format data, reboot your device into recovery again and transfer LOS, gapps and all files you need.
Format data kills the storage.
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes I did that and it worked, unmounting and remounting helps detect the storage in PC
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes that works. Tried it myself but prefer to reboot into recovery again.:laugh:
Finally Successful
After a long post I have finally finished the process successfully. This was pretty educational for me since I didn't understand any of this at the start I would like to thank everyone who reply's and all the information that you have provided.
need help guys, i stuck in bootloop.
- fastboot rom global china V10.3.17.0 PFKCNXM
- fastboot twrp 3.3.1
- format data
- flash vendor image cn 10.4.6.0
- wipe cache/dalvik
- flash lineage os
- flash gapps nano
- reboot
- stuck bootloop
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.