How I can disable encryption in TWRP? That I can see sdcard and flash files etc.
Editing vendor.img didn't work.
Flash dm verity patched boot and use force encrypt disabler in twrp after formatting data in twrp
Dadud said:
Flash dm verity patched boot and use force encrypt disabler in twrp after formatting data in twrp
Click to expand...
Click to collapse
I don't have option "force encrypt disabler" in TWRP. And where I can find dm verity patched boot.img for plus version?
Never mind you Plusser ? drat
Related
I found a zip called magisk FDE 16.7
It removed force encryption from self encrypting roms
How can I get the updated zip ,I think it was unofficial
It's different from the normal official magisk zip, it does not disable force encryption
https://mega.nz/#!23J3SALD!ufZYJRdn_jzzMwk0qt4zUtGef9rO14ZlrDi3Rw0aPUI
Official Magisk does not remove force encryption if it detects that your device is encrypted.
But, you can set it to remove forced encryption if you want. Either make sure "Preserve forced encryption" is disabled in the Magisk Manager when you patch a boot image, or run the following command in TWRP terminal before flashing the Magisk zip:
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
A tip: Be careful with zips that you just "find"...
Didgeridoohan said:
Official Magisk does not remove force encryption if it detects that your device is encrypted.
But, you can set it to remove forced encryption if you want. Either make sure "Preserve forced encryption" is disabled in the Magisk Manager when you patch a boot image, or run the following command in TWRP terminal before flashing the Magisk zip:
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
A tip: Be careful with zips that you just "find"...
Click to expand...
Click to collapse
so it will disable "Preserve forced encryption" from magisk on clean flash of roms?
will it patch fstab* files as well? ( for trebilize or non- treblize roms)
I don't know about other users, but when I installed magisk on asus zc554kl, I have to format data, coz system can not be loaded. Then, TWRP lost access to /data partition too.
I think I have solution for this problem. It allows TWRPs decrypt data and transfer them from original system.
The problem is Magisk patchs kernel in boot.img, so new boot image can not decrypt data and you need format data.
BUT I Suggest those steps (it worked for me):
1. Magisk should create 2 new images : boot and recovery
Firstly it unpack boot, patches kernel and build boot, as usual.
But Magisk also should use same patched kernel for repacking TWRP/recovery. In this case decrypt from TWRP will be supported.
Dreamject said:
I don't know about other users, but when I installed magisk on asus zc554kl, I have to format data, coz system can not be loaded. Then, TWRP lost access to /data partition too.
I think I have solution for this problem. It allows TWRPs decrypt data and transfer them from original system.
The problem is Magisk patchs kernel in boot.img, so new boot image can not decrypt data and you need format data.
BUT I Suggest those steps (it worked for me):
1. Magisk should create 2 new images : boot and recovery
Firstly it unpack boot, patches kernel and build boot, as usual.
But Magisk also should use same patched kernel for repacking TWRP/recovery. In this case decrypt from TWRP will be supported.
Click to expand...
Click to collapse
well that only works in the boot to system, once boot to other partition access is lost
Hi guys
I ask for something that I didn't understand so well, but now every time I change roms do I have to flash the DM verity zip? Because the last time I tried the lineage 17 the system was not able to boot I think because of this dm-verity zip that I didn't flash and the internal archive encryption.
However, my internal archive is not encrypted because the first time I installed xiaomi.eu I made Format data and typed Yes and then I also made all the wipes and installed the ROM in this way I removed the encryption from the archive interior right?
But do I still need to flash the DM verity zip every time I switch Rom?
For example, now I want to try havoc 3.0.
I have a xiaomi mi 8 with the latest wikley from xiaomi.eu 9.10.24
Up!
Inviato dal mio MI 8 utilizzando Tapatalk
Since your Filesystem is not encrypted, you have to do that.
The War Profiteer said:
Since your Filesystem is not encrypted, you have to do that.
Click to expand...
Click to collapse
But do I have to flash the DM verity zip every time I update my Rom? (when I update my rom I don't do a clean install I only do Wipe Cache and Devilk)
Or should I flash it only when I change ROM then after a clean installation?
(When I change ROM I make wipe data and system)
andrea0807 said:
But do I have to flash the DM verity zip every time I update my Rom? (when I update my rom I don't do a clean install I only do Wipe Cache and Devilk)
Or should I flash it only when I change ROM then after a clean installation?
(When I change ROM I make wipe data and system)
Click to expand...
Click to collapse
Probably yes.
I'm just going to say this again, DM-Verity stands for "D"-Device "M"-Mapper verity (verification). This protection looks at hashes for the mounted partitions and kernel to make sure they have not been modified. If the hashes don't match, the boot chain fails to load. Once again, this really doesn't have to do with Encryption. Encryption was sometimes included in the DM-Verity ZIP files also called FEC remover (Forced Encryption Remover). Even though the are a lot of times included in the 'DM-Verity" remover zip files, they are separate things! If you modify the stock MIUI partitions at all, it needs to have the DM-Verity removed -but doesn't have to have the FEC (encryption) removed. These forums are full of everyone saying flash the DM-Verity to remove encryption, which is only correct in a sense because most of the ZIP files floating around does in-fact remove the FEC (forced encryption) at the same time. If i am running modified stock, i want to keep encryption and just remove the verity bit that fails.
Info on DM-Verity:
https://source.android.com/security/verifiedboot/dm-verity
./
Agimax said:
I'm just going to say this again, DM-Verity stands for "D"-Device "M"-Mapper verity (verification). This protection looks at hashes for the mounted partitions and kernel to make sure they have not been modified. If the hashes don't match, the boot chain fails to load. Once again, this really doesn't have to do with Encryption. Encryption was sometimes included in the DM-Verity ZIP files also called FEC remover (Forced Encryption Remover). Even though the are a lot of times included in the 'DM-Verity" remover zip files, they are separate things! If you modify the stock MIUI partitions at all, it needs to have the DM-Verity removed -but doesn't have to have the FEC (encryption) removed. These forums are full of everyone saying flash the DM-Verity to remove encryption, which is only correct in a sense because most of the ZIP files floating around does in-fact remove the FEC (forced encryption) at the same time. If i am running modified stock, i want to keep encryption and just remove the verity bit that fails.
Info on DM-Verity:
https://source.android.com/security/verifiedboot/dm-verity
./
Click to expand...
Click to collapse
Thanks for clearing that up, there is a lot of conflicting information out there and it's difficult finding information that is currently valid and applicable to our phones.
Edit :
I should add that I never flash dm-verity and that I do not have issues. However, I also do not change the boot, except for Magisk.
I got a new phone two days ago with zui rom installed
This rom uses forced encryption that can't be decrypted through twrp recovery.
Yesterday i went through an issue with a module that froze android after boot and couldn't unlock it to remove the module!
Data partition is encrypted under recovery and i can't remove the module manually through file manager and the only option i had is to format data partition which result in a loss of all files.
For future if i went through such issue; is there a way i could remove or disable magisk through recovery without mounting data partition?
allouh said:
I got a new phone two days ago with zui rom installed
This rom uses forced encryption that can't be decrypted through twrp recovery.
Yesterday i went through an issue with a module that froze android after boot and couldn't unlock it to remove the module!
Data partition is encrypted under recovery and i can't remove the module manually through file manager and the only option i had is to format data partition which result in a loss of all files.
For future if i went through such issue; is there a way i could remove or disable magisk through recovery without mounting data partition?
Click to expand...
Click to collapse
You should be able to just flash the boot.img
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
You should be able to just flash the boot.img
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I tested this while writing this post , i flashed boot.img through fastboot but it gave me Red Boot screen error (Device Corrupt) and when device run magisk still working
1 .Make sure your device has unlocked bootloader
2. Download Stock A10(in ASUS website) & modify updater script ( Remove everything before uiprint)
3. Reboot to Recovery and wipe data cache dalvik
4. Install Stock A10 zip
5. Flash Magisk 20.4 then dm verity 08-18 zip
6. Reboot to system after doing those
7. After rebooting go to recovery again
8. Take boot img backup(this step is for precaution otherwise if any problem of boot loop u will need to do again)
9. After backing up Flash gsi img (must be arm64 AB and don't forget to extract it)
10. Flash Magisk 20.4 then dm verity 08-18 zip again
11. Reboot to system after doing those
Note: if doesn’t boot or u have bootloop reflash boot img
BY AP XD
Hit Thanks if I had helped You.
FEEL free to PM me.
GSI: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Magisk 20.4 : https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
DM verity forceencrypt disabler : https://drive.google.com/file/d/1b2DUcWpDLM5lW1oPwdHshH6CEdvL9ZxM/view?usp=sharing
AP#xda said:
1 .Make sure your device has unlocked bootloader
2. Download Stock A10(in ASUS website) & modify updater script ( Remove everything before uiprint)
3. Reboot to Recovery and wipe data cache dalvik
4. Install Stock A10 zip
5. Flash Magisk 20.4 then dm verity 08-18 zip
6. Reboot to system after doing those
7. After rebooting go to recovery again
8. Take boot img backup(this step is for precaution otherwise if any problem of boot loop u will need to do again)
9. After backing up Flash gsi img (must be arm64 AB and don't forget to extract it)
10. Flash Magisk 20.4 then dm verity 08-18 zip again
11. Reboot to system after doing those
Note: if doesn’t boot or u have bootloop reflash boot img
BY AP XD
Hit Thanks if I had helped You.
FEEL free to PM me.
GSI: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Magisk 20.4 : https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
DM verity forceencrypt disabler : https://drive.google.com/file/d/1b2DUcWpDLM5lW1oPwdHshH6CEdvL9ZxM/view?usp=sharing
Click to expand...
Click to collapse
is it stable enough for daily usage
ankushlohiya said:
is it stable enough for daily usage
Click to expand...
Click to collapse
GSI is expected to have bugs.
Like phh based gsi has the Bluetooth audio bug.
But yes oneplus gsi doesn't have that bug.
It depends on your choice of GSI.
How to edit stock zip
And remove everything before ui print