Question TWRP - Failed to mount '/data' (Invalid argument) [solved] - Redmi Note 10 Pro

Hello, I've been trying to install Project Elixir after finally unlocking bootloader today, but i've just been running into a whirlwind of error messages. I hope anyone can help me here, as I feel quite stuck.
The guide I followed so far:
[GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP
The Project Elixir version I downloaded: ProjectElixir_1.5_sweet-12.0-20220314-1523-OFFICIAL.zip
Steps I took:
So I unlocked bootloader on stock rom, installed magisk and rooted my phone with the Project Elixir boot.img (this might be where things went sideways, now that I think about it), then installed TWRP so I could boot into recovery (Couldn't figure out whether or not magisk allows you to boot into recovery to install custom roms), and this is where I'm currently at.
I cannot:
-Wipe (gives failed to mount data error message)
-Install zip ("Error installing zip file 'external_sd/Download/<projectelixirzipfile>'
-repair or change file system (Error message: Invalid Partition Selection)
I've formatted the phone again, but that doesn't do anything. The only thing I know that i've done is unlock the phone, as developer options says the phone is unlocked. I've googled around, and I cannot find anything that works. Any help here would be greatly appreciated.
Edit: fixed the issue, and am now in the process of flashing project elixir.
failed to mount data fix (just me being a moron, mostly)
install zip error fix
Edit #2 : after flashing project elixir, on reboot I am booting straight into TWRP, so there's another issue for me to look into. fun stuff.
Edit #3: now i'm stuck on fastboot. how about I just tap out for the day, before my phone obliterates.

dekisokonai said:
Hello, I've been trying to install Project Elixir after finally unlocking bootloader today, but i've just been running into a whirlwind of error messages. I hope anyone can help me here, as I feel quite stuck.
The guide I followed so far:
[GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP
The Project Elixir version I downloaded: ProjectElixir_1.5_sweet-12.0-20220314-1523-OFFICIAL.zip
Steps I took:
So I unlocked bootloader on stock rom, installed magisk and rooted my phone with the Project Elixir boot.img (this might be where things went sideways, now that I think about it), then installed TWRP so I could boot into recovery (Couldn't figure out whether or not magisk allows you to boot into recovery to install custom roms), and this is where I'm currently at.
I cannot:
-Wipe (gives failed to mount data error message)
-Install zip ("Error installing zip file 'external_sd/Download/<projectelixirzipfile>'
-repair or change file system (Error message: Invalid Partition Selection)
I've formatted the phone again, but that doesn't do anything. The only thing I know that i've done is unlock the phone, as developer options says the phone is unlocked. I've googled around, and I cannot find anything that works. Any help here would be greatly appreciated.
Edit: fixed the issue, and am now in the process of flashing project elixir.
failed to mount data fix (just me being a moron, mostly)
install zip error fix
Edit #2 : after flashing project elixir, on reboot I am booting straight into TWRP, so there's another issue for me to look into. fun stuff.
Edit #3: now i'm stuck on fastboot. how about I just tap out for the day, before my phone obliterates.
Click to expand...
Click to collapse
It looks like that you've tried Android 12 version?
With 12 and TWRP (until now, there's no recovery which can encrypt 12).you can only side load or you flash DfE for encryption.....

Laptapper said:
It looks like that you've tried Android 12 version?
With 12 and TWRP (until now, there's no recovery which can encrypt 12).you can only side load or you flash DfE for encryption.....
Click to expand...
Click to collapse
Thank you for your reply. I gotta be honest; not sure what that means, but I flashed the orangefox recovery img, then it booted into orangefox, and after formatting data and rebooting, I launched into project elixir, so for now I think i'm good.
This thread can be marked as solved.

Related

Not able to install any Android 9.0 based ROM's

I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Did you tried another recovery? Try Batik Recovery!
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status
Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again
Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.
Decrypt ur phone first then flash, use twrp vendor
athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.

Having trouble with TWRP error 1 "Cannot mount /system"

Hello, everyone!
I hope anyone can help me.
Yesterday I assisted with rooting and flashing a Mi 9 T Pro with Xiaomi.eu firmware.
Here are the steps which were done:
1. Unlocking bootloader via MiFlash Tool.
2. Flashing TWRP (this one: https://androidfilehost.com/?fid=6006931924117906979)
3. First trouble: It only booted once into TWRP with "fastboot boot recovery xxx.img, after formatting data and a restart of TWRP it refused to get access again, neither with a command nor with hardware keys. It was stuck in fastboot.
4. With the MiFlash Tool I reverted to the stock global (this one: http://bigota.d.miui.com/V10.3.1.0....M_20190805.0000.00_9.0_global_135788d537.tgz)
5. After successfully flashing the stock ROM, I downloaded and flashed this TWRP: https://www.androidfilehost.com/?fid=1899786940962577905
6. Flashing this version of TWRP went perfectly fine.
7. In TWRP I formatted data again. I restarted TWRP and copied the following files to storage:
ROM: https://androidfilehost.com/?fid=1899786940962578113
Magisk 19.2.zip
Disable_dm verity_ForceEncrypt
8. I wiped Dalvik, cache, system and data.
9. I flashed ROM - it went through without problems
10. I tried to flash the dm verity, then an error occurred (please see the attached picture).
Can you please tell me what I'm doing wrong? Root is mandatory for me, I definitely need it.
I'm looking forward to your input and your help, it's very appreciated!
try to unmount system then flash it again
SkipperRyujin said:
try to unmount system then flash it again
Click to expand...
Click to collapse
Thanks for your input. I tried that, unfortunately this didn't work.
But I found the solution a few minutes ago:
I downloaded TWRP 3.3.1-13 (one version newer) and flashed it inside of my old TWRP. I rebooted to recovery again and then flashed Magisk without problems.
(The dm verity still refuses to install but the phone is booting and running.)
Well, it always work for me, or simply reboot recovery also work. Try wzsx twrp, it has remove DM verity & forced encryption remover in advanced menu

GUIDE How to Instal GSI ROM- Havoc-OS-v4.X-Official Android 11 On Redmi 8

Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....
letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry
Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?
letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.
letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse
Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11
letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.

[Guide] Enable encryption on a custom ROM which has it disabled by default

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.

Question Stuck on mi logo after rom installation failed

Hi,
I was on CDroid 9 and I decided to install Project Elixir 3.3 instead.
On twrp I cleaned flash but I didn't Dirty flashed.
So it didn't work and I was stuck in recovery mode.
Then I dirty flashed but it failed to mount system, media ...
I was stuck there and I didn't know what to do.
It worked but I had to go to the native recovery. I still don't know what went wrong on twrp.
Could you give me some advices for the next time ?
Thanks guys!
don't make twrp permanent.
Boot into twrp, install projectelixir, and reboot, this should work.
Deleted

Categories

Resources