So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0
Backup your stock recovery per this post. If you are too lazy, I can upload my backup from .104 build (C432) to Mega.
Download twrp_bkl_0.7.img from this post and place it in same directory with your ADB.
After successful backup as precaution disable any locks like pattern/PIN/password/fingerprint, reboot to bootloader (fastboot):
Code:
adb reboot bootloader
Then flash new TWRP recovery:
Code:
fastboot flash recovery_ramdisk twrp_bkl_0.7.img
After successful flash reboot device and immediately after confirming command below unplug USB cable and HOLD and keep holding VOLUME UP button, if you won't the new recovery will be overwritten by stock and you can try again.
Code:
fastboot reboot
Tested by myself on Honor 10 8.1.0.104 (C432) with unlocked bootloader and installed already Magisk 16.4 with Magisk manager 5.7.0, Magisk ramdisk persisted after installing TWRP recovery, system boots normal.
Next step after unlocking BL, installing Magisk, installing TWRP recovery -> flashing GSI AOSP, LOS or RR. Only reason I bothered with installing TWRP was that GSI image of LOS and RR don't include opengapps, only AOSP does, so without TWRP you can't have opengapps with these two GSI ROMS.
PeterMarkoff said:
Backup your stock recovery per this post. If you are too lazy, I can upload my backup from .104 build (C432) to Mega.
Download twrp_bkl_0.7.img from this post and place it in same directory with your ADB.
After successful backup as precaution disable any locks like pattern/PIN/password/fingerprint, reboot to bootloader (fastboot):
Code:
adb reboot bootloader
Then flash new TWRP recovery:
Code:
fastboot flash recovery_ramdisk twrp_bkl_0.7.img
After successful flash reboot device and immediately after confirming command below unplug USB cable and HOLD and keep holding VOLUME UP button, if you won't the new recovery will be overwritten by stock and you can try again.
Code:
fastboot reboot
Tested by myself on Honor 10 8.1.0.104 (C432) with unlocked bootloader and installed already Magisk 16.4 with Magisk manager 5.7.0, Magisk ramdisk persisted after installing TWRP recovery, system boots normal.
Next step after unlocking BL, installing Magisk, installing TWRP recovery -> flashing GSI AOSP, LOS or RR. Only reason I bothered with installing TWRP was that GSI image of LOS and RR don't include opengapps, only AOSP does, so without TWRP you can't have opengapps with these two GSI ROMS.
Click to expand...
Click to collapse
Nice work. ?
tried to install GSI RR OS, but ending in bootloop, also even after resizing system partition to maximum (TWRP / wipe / resize) opengapps still showing error 70 about insufficient space (which makes no sense, so they really seem to have wrong detection of A/B instead of A for Huawei/Honor devices), though these gzr gapps seem to install successfuly, now if I could figure out the damn bootloop
potential reasons for bootloop - previously installed magisk, wiped also system not only data/cache, installed through fastboot while TWRP there and not only stock recovery, ???
edit: i guess will try flash GSI through TWRP again, quite a waste time to wait each time like 9-10 minutes to find out it can't boot
edit 2: so even flashing through TWRP doesn't help, just stuck on android animation for 10 minutes and then it restarts (and even if you do fatory reset through huawei erecovery it doesnt change anything). maybe can try to restore everything and not wipe system before installing, just factory reset through TWRP (though I remember I read somewhere it's not reliable and it is better to do it through system, but I think that one wipe also internal storage which I wanna avoid)? back to rooted EMUI with TWRP for now, don't have time to try various combinations
edit 3: flashing over TWRP backup without wiping system doesn't help, so it seem it's gonna be magisk or replaced stock recovery i guess, otherwise no idea
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
PeterMarkoff said:
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
Click to expand...
Click to collapse
Don't be disappointed the lack of feedback from users is not many power users have got their hands on this model.
And also we are having different builds.
From the day one I am trying to rebrand my device but no success .
Once I have rebranded to EU I will try and let you know.
Did you flash open gapps nano package through twrp in gsi image?
Did it give you the same error?
tried just pico opengapps as on all phones i flash, that's the smallest, but always end up with error 70 not enough space despite resized system partition in TWRP and many GB available, the other unofficial GZR zero gapps build i mentioned seem to be flashed successful in TWRP, but in any case no luck with booting
PeterMarkoff said:
tried just pico opengapps as on all phones i flash, that's the smallest, but always end up with error 70 not enough space despite resized system partition in TWRP and many GB available, the other unofficial GZR zero gapps build i mentioned seem to be flashed successful in TWRP, but in any case no luck with booting
Click to expand...
Click to collapse
Did you format your phone before trying GSI ?
Try formatting phone and remove some system apps and then flash gapps it will mostly solve the problem.
PeterMarkoff said:
BTW the lack of feedback here and trying from other users it's very depressing. they boasted million phone sales and i am the only one in the whole world trying to install TWRP and GSI ROM on this phone?
Click to expand...
Click to collapse
Don't be upset – e.g. I didn't receive my Honor 10 yet. You won't be the only one for sure, you're just the first one to do it, which is super nice for others because it motivates them to do so as well!
Just wondering: does it make a difference for TWRP wether I own the 6gb or 4gb version?
miststudent2011 said:
Did you format your phone before trying GSI ?
Try formatting phone and remove some system apps and then flash gapps it will mostly solve the problem.
Click to expand...
Click to collapse
I did factory reset (data, both cache) and also wiped system partition, gapps would be the least issue, as I said that GZR should work, but my system doesn't boot, no matter how times I wipe everything through TWRP or stock recovery after flashing system.img, since they say it's normal to hang at first boot and then wipe and then it should boot, but it doesn't work for me. also of course tried to power off phone since some people said it helps to do it after flashing. what I haven't done it's fastboot -w which should be some better wipe. some people say also you should remove magisk ramdisk, though I forgot to back up original, backed up just stock recovery. and also I haven't tried to flash everything with stock recovery, though first flash I did was through fastboot anyway and not through TWRP and it didn't make difference
so last few things left to try:
- fastboot -w for total wipe of data (better than TWRP? though it should be same as Format data in TWRP which wipe everything including internal storage which I wanna avoid since backing up 15GB TWRP backup file it's kinda annoying and my system has problem to do it)
- flash with stock recovery (I have backup, no big deal)
- remove magisk ramdisk and flash with stock ramdisk (forgot to make backup, can't replace)
though I am tired of it for now, spend last night like 4 hours dealing with it until 2AM and I also need to take care of children
vollkornbaguette said:
Don't be upset – e.g. I didn't receive my Honor 10 yet. You won't be the only one for sure, you're just the first one to do it, which is super nice for others because it motivates them to do so as well!
Just wondering: does it make a difference for TWRP wether I own the 6gb or 4gb version?
Click to expand...
Click to collapse
I don't think RAM has something to do with anything, but that sounds like Chinese version since EU has always 4GB and only difference is storage, so you will have different ROM
PeterMarkoff said:
(...)
so last few things left to try:
- fastboot -w for total wipe of data (better than TWRP?)
- flash with stock recovery (I have backup, no big deal)
- remove magisk ramdisk and flash with stock ramdisk (forgot to make backup, can't replace)
Click to expand...
Click to collapse
So I just read more about the GSI/Treble stuff and it said somewhere that modifications like Magisk probably lead to problems with the GSI flash.
Which is why I would try to get rid of the magisk ramdisk first.
I'm not an expert in this at all but maybe this helps.
---
PeterMarkoff said:
I don't think RAM has something to do with anything, but that sounds like Chinese version since EU has always 4GB and only difference is storage, so you will have different ROM
Click to expand...
Click to collapse
Indeed I bought the chinese 6gb RAM Version (hope this won't turn out as a big mistake)
vollkornbaguette said:
So I just read more about the GSI/Treble stuff and it said somewhere that modifications like Magisk probably lead to problems with the GSI flash.
"Your device is free of any heavy modifications such as the
Click to expand...
Click to collapse
yeah, now if someone could extract for me from 0.104 firmware for C432 that stock ramdisk, because I have some problems with mega to download it and I just need the stock ramdisk, nothing else, I have stock recovery backup but forgot to make ramdisk backup
edit: completely forgot there is option to "Completely uninstall" in Magisk manager, so tried it though even after restart with magisk manager missing i could still use root apps, so not sure how exactly this "complete uninstall" works, but anyway giving it a try after this and wiping data, installed system.img again, again wiped, rebooted and as usual loading and loading and nothing, seem can't further continue without copy of stock ramdisk to flash, tried downloading the big update from mega to extract it but it always fail for me to download, same with trying to copy my TWRP backup because for sure ain't gonna doi fastboot -w and setting up everything from scratch in case even this doesn't help, if I knew it works for sure and it will load new system which I will have to set up then no problem, but in this case...
edit 2: tried to replace magisk ramdisk with ramdisk from Honor View 10 BKL09 (same as our working TWRP) but it seem I end up after flashing it, wiping and flashing system.img in TWRP/erecovery bootloop, it's not showing android booting logo like before (but hey at least no need to wait 10 minutes to find it's fail) and either go to huawei ercovery, if I perform factory reset there then it boots to TWRP, but can't boot anywhere else besides these two
pass
I requested this image. Recovery has been established. When I enter the recovery, it requires a password to decrypt the system partition, I enter it (the same after switching on the phone), but a message is displayed that the password is incorrect. help me please.
told you in OP disable all passwords before flashing
PeterMarkoff said:
yeah, now if someone could extract for me from 0.104 firmware for C432 that stock ramdisk, because I have some problems with mega to download it and I just need the stock ramdisk, nothing else, I have stock recovery backup but forgot to make ramdisk backup
edit: completely forgot there is option to "Completely uninstall" in Magisk manager, so tried it though even after restart with magisk manager missing i could still use root apps, so not sure how exactly this "complete uninstall" works, but anyway giving it a try after this and wiping data, installed system.img again, again wiped, rebooted and as usual loading and loading and nothing, seem can't further continue without copy of stock ramdisk to flash, tried downloading the big update from mega to extract it but it always fail for me to download, same with trying to copy my TWRP backup because for sure ain't gonna doi fastboot -w and setting up everything from scratch in case even this doesn't help, if I knew it works for sure and it will load new system which I will have to set up then no problem, but in this case...
edit 2: tried to replace magisk ramdisk with ramdisk from Honor View 10 BKL09 (same as our working TWRP) but it seem I end up after flashing it, wiping and flashing system.img in TWRP/erecovery bootloop, it's not showing android booting logo like before (but hey at least no need to wait 10 minutes to find it's fail) and either go to huawei ercovery, if I perform factory reset there then it boots to TWRP, but can't boot anywhere else besides these two
Click to expand...
Click to collapse
If you want, i have all the files of the C432 update but idk in wich .zip, folder the ramdisk is stored.
I can send on several clouds.
PeterMarkoff said:
told you in OP disable all passwords before flashing
Click to expand...
Click to collapse
Hey did you restore your device are you still struck at boot screen?
If yes try this method.
https://forum.xda-developers.com/huawei-p20/development/rebrand-huawei-p20-eml-l29-eml-l09-t3779283
How to GO back to stock emui(India) after i flash a treble rom? Do i need to backup using some tool?
PLease someone tell me
srharshajava said:
PLease someone tell me
Click to expand...
Click to collapse
The problem is currently we don't have full
ROM to revert to stock and if we brick our device there is no proper way to revert to stock.
Our model even doesn't have SD card support.
Just wait for some time for someone to provide proper way.
When i flash a treble rom, I have a bootloop. I returned back with eRecovery directly on the phone.
miststudent2011 said:
The problem is currently we don't have full
ROM to revert to stock and if we brick our device there is no proper way to revert to stock.
Our model even doesn't have SD card support.
Just wait for some time for someone to provide proper way.
Click to expand...
Click to collapse
We do have a way to download full ROM.
http://pro-teammt.ru/firmware-database/?firmware_model=COL-L29C432
1. Search here for your exact model (change numbers after C432 to find ROM for your phone) and search for your rom version (B104 or B120)
2. Double click on "filelist" on the same row as FullOTA-MF
3. From filelist link menu download update.zip file (it should be really big, like 2+GB)
3. Extract UPDATE.APP file somewhere (eg. Desktop)
4. In settings of HuaweiUpdateExtractor (link: https://forum.xda-developers.com/showthread.php?t=2433454) uncheck "verify header checksum" and open UPDATE.APP
5. Extract any img (Be it ramdisk.img, ramdisk_recovery.img or system.img) file that you need from UPDATE.APP via HuaweiUpdateExtractor
You just got whoole stock rom and img files that you can flash. Tested by myself with flashing back original ramdisk, ramdisk_recovery and system.img and everything worked well.
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.