Database Users

Flashed TWRP and rooted, now my file system is encrypted?

I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?

I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.

Twerkules said:
I somehow got my filesystem encrypted when I flashed TWRP and rooted. When I try to boot into TWRP, I have to enter a password to be able to see anything or do any modifications. What happened?
Click to expand...
Click to collapse
bhint15 said:
I didnt have this problem on my Axon but googled.
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
I have no idea if this will help you or not but it will wipe data so your phone will be factory reset. Do at your own risk.
Click to expand...
Click to collapse
This is from the Thread @bhint15 posted ,
Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....

This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.

RojasTKD said:
This may give you some insight.
https://youtu.be/y0fHGJY-vFE
For me it's the Axon 7. I like the bigger res screen, the upcoming daydream compatibility and superior audio and non-Apple like OS.
The Honor 8 dies seem to have a better camera, but I can live with that. Plus I have an LG G5 for when I want photos.
You just have to decide witch Frasier is more important to you.
Click to expand...
Click to collapse
Wrong Thread mate LoL,

DrakenFX said:
Wrong Thread mate LoL,
Click to expand...
Click to collapse
What the neck how did u end up here....
Disregard ?

DrakenFX said:
This is from the Thread @bhint15 posted ,
and the reason why ask for password is cuz Axon 7 Data/Storage is Automatically encrypted out of the box, that's why you don't or not going to find any sort of encryption data setting under Settings and That's the reason a lot of users here have issues trying to get back to stock or something similar.....
Click to expand...
Click to collapse
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?

Twerkules said:
Alright, I managed to be able to write to /system temporarily by formatting the Data partition in TWRP, then rebooting back into TWRP. However, after rebooting into OS and setting up my phone, I rebooted into TWRP and was faced with the encryption password prompt again! Does the filesystem just re-encrypt itself when you start the OS, or am I doing something wrong?
Click to expand...
Click to collapse
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..

HonestOtter said:
I gave up for now. I tried for 4 days to fix this. In the end I have 30 days to return the phone. Hopefully someone will figure out a work around for this issue. I really like using twrp. I have not read a comment on here of anyone being able to boot into system then back into twrp with out having to enter a password to decrypt. I hope someone out there can do it and they figure out a way to fix it for the rest of us..
Click to expand...
Click to collapse
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.

runderekrun said:
When does twrp prompt for password? I just booted into TWRP and it didn't prompt me. Then I simply booted back into the rom. Never prompted for a password.
Click to expand...
Click to collapse
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.

Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
Which bootloader unlock did you do? I wonder, why would this not happen to me but happen to you? I am willing to test anything that needs to be tested.

You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!

XblackdemonX said:
You cannot fix that. Like DrakenFX said, the partition encrypts itself in the OS. You cannot disable/bypass this!
Click to expand...
Click to collapse
Auto-encrypted can be disabled but that's way, way out of my league, need to rebuild boot. Img with that feature disabled.

There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.

Twerkules said:
As soon as I get into TWRP it asks me for the password. I can continue into TWRP but I can't mount or modify the /system partition (it reads as 0b in TWRP File Browser). No idea how to fix, but I'm glad it's not just me having this issue.
As of right now, it looks like we are going to have to wait for custom ROMs for a fix, unless TWRP gets an update just for this. I saw a thread here asking users for info for final tweaks on a CM13 port to the Axon 7.
Click to expand...
Click to collapse
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
peramikic said:
There are two different scenarios that will be in play here. Is the bootloader unlocked or not. If the bootloader is unlocked then boot.img can be patched with the zip from idlekernle that disables the dm-verity and fstab. You cannot do this if your BL is locked, because it will modify the signed boot.img that that provides root, and will not boot anymore.
After it's patched, the system will not encrypt after /data wipe and TWRP will access it without problem. The downside is no encryption.
For the BL locked crowed, the /data has to be reformatted after flashing new rooted boot.img. This image also enforces encryption so one way to solve this would be for @tenfar to provide us with signed boot.img that set encryption of as well as. Otherwise the TWRP will need a password to decrypt /data if it can't use the default_password. In this case you should be able to enter the same pin you have setup for lock screen to decrypt the main encryption key.
The system re-encrypts itself on every system start after factory reset or /data format because of the forceencrypt flag in fstab, so the pin will be needed as long as that's the case. While TWRP should be able to try to decrypt with "default_password" in case you have not setup any on lockscreen, this sometimes fails, so having a pin on lockscreen usually helps. The cause is most likely that /cryptkey is altered somehow and TWRP can't use it. Wiping /data and rebooting should generate an fresh /cryptkey. I have been able to just flash modded recovery while still on stock boot and backup the /data with no key.
/system should not be encrypted ever since it would make block level OTA impossible to do. Why TWRP is not mounting it or seeing it 0b is a separate question.
Click to expand...
Click to collapse
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.

HonestOtter said:
That would be dreamy. I have no issues waiting, fingers crossed.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
Well i have formatted my data maybe 30 times with all sorts of different recoveries and boot images. My original boot image is long gone so hopefully that isn't the key. I also don't use a lock screen, I guess I could if it unlocks the data, but I certainly wouldn't want to keep using a lock screen. Anyways I am done with the phone for now, will revisit it when someone fixes posts they had the decrypt PW issue and fixed it.
Click to expand...
Click to collapse
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?

peramikic said:
See if you can set the pin, go into TWRP and us it. If it works, go back to OS and remove lockscreen, set to none and then go back to TWRP and see if it still asks for one. Did you run TWRP in read only mode or did you swipe to mount as RW?
Click to expand...
Click to collapse
I assume you mean the lock screen pin? I set a lock screen pin of 1234, but "password failed, please try again". So that didn't work. Is there a different pin for the encryption?
***update
That sucked. I don't use a lock screen but after I tried the pin it won't let be go back to none for the lock screen. I was just starting to use this phone to, now its back to the old phone because I can't use a phone with a lock screen . So sad. Hopefully someone figures out a solution to all this security crap.

I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.

zigzampow said:
I'm having the same issue on B27. Do a factory Reset, then a Format, and after it boots to the OS, the data is encrypted again. I'd be somewhat ok with it but I'm not clear on how to install things like Xposed if the drive is encrypted? I assumed ADB SIDELOAD... but not through encryption.
If the answer is "I don't know" -- then can someone help me restore to stock B27. I have a locked bootloader.
Click to expand...
Click to collapse
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine

mmamedov said:
Xposed should install just fine if you're getting the message in TWRP. Id you're getting the encryption message after the phone is booted and can't access the phone, then you need to format data, then install Xposed so you can use the phone.
Some zips like SuperSU zip will not be able to be installed when the partition is encrypted. Xposed zip should install just fine
Click to expand...
Click to collapse
But if TWRP cannot access the encrypted data, how can one select and flash the TWRP flashable zip that accompanies the Xposed APK? Is the only solution to sideload? I see the option in TWRP but I am not familiar with how to do it.

Want to encrypt data, can I still disable magisk module via TWRP?

Hi, thanks for all the information here.
Thanks to the guides, I was able to downgrade, backup TA, upgrade, build personal kernel, install twrp, working android pay.... everything is good. But:
I have tested out some modules for Magisk, two I wanted to use boot me in a boot loop/stuck on boot.
I can fix this using TWRP, I just use mount_magisk stored in my download on internal storage.
Then I disable the 'bad' module, by typing in the terminal: /magisk/<module folder>/disable
BUT!
This only works because my data is decrypted.
I want to encrypt my data.
It is true we still don't have a TWRP that supports our encryption?
If I encrypt, is there anyway to disable a bad magisk module?
I think magisk is stored in the boot, correct? So it is not in data, so it does not matter if data is encrypted or not?
I hope someone can clear up some of my worries.
Thanks

While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.

ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
Ok, so if I wanted to recover my system, I could just reflash boot (my kernel)?
I would have to install magisk again but that is ok.
But would I even be able to install magisk if my data is encrypted?
I think v12 can be installed if no access to /data, but v13 not?
Thanks

ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.

voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
I don't have an encrypted partition. Could anybody with encrypted partition try it?

voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
Yes it does say that, but it is talking about fw version 34.1.A.1.198 - which is marshmallow right?
From what I understand TWRP was fine with XC's encryption in marshmallow, but with nougat it doesn't work.
So I think (that version of) TWRP will not work. (but I have not tested myself, but I read a post somewhere saying it didn't)

Oneplus 5 shutting down after the OTA

Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk

Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?

strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.

Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:

strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?

Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.

https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem

I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!

TWRP isn't asking for my password

On my Nexus 6P I am using TWRP - twrp-3.3.1.0-FBE-10-angler.img I went from DerpFest (which was not encrypted) to a clean install of Evolution X (both Android 10) and now after install I went back to recovery to get root using Magisk and I see that my phone has been encrypted and TWRP doesn't ask for any credentials and only shows internal storage as encrypted folders. Does anyone know how to fix this? Can I get root with Magisk using OTG? I am not sure how it will install with the encryption and I don't want to brick the phone.
Update: Ok I was able to use OTG with a USB to load Magisk.zip and get root. But when I boot to TWRP it doesnt ask me for any passwords or credentials. So I don't know how I can remove the internal storage encryption.

nohart said:
On my Nexus 6P I am using TWRP - twrp-3.3.1.0-FBE-10-angler.img I went from DerpFest (which was not encrypted) to a clean install of Evolution X (both Android 10) and now after install I went back to recovery to get root using Magisk and I see that my phone has been encrypted and TWRP doesn't ask for any credentials and only shows internal storage as encrypted folders. Does anyone know how to fix this? Can I get root with Magisk using OTG? I am not sure how it will install with the encryption and I don't want to brick the phone.
Update: Ok I was able to use OTG with a USB to load Magisk.zip and get root. But when I boot to TWRP it doesnt ask me for any passwords or credentials. So I don't know how I can remove the internal storage encryption.
Click to expand...
Click to collapse
Format data but you will loose everything.

ttocs99 said:
Format data but you will loose everything.
Click to expand...
Click to collapse
Ya and I take the chance after spending hours re-installing the rom that it just gets encrypted again. Right now I have root and the phone is working fine. The only part as far as I can tell that is encrypted is the Internal Storage. The problem is that when I boot into TWRP it isn't asking for a password or my swipe pattern and if I go to the terminal in TWRP and type - twrp decrypt <your password> doesn't work either. I even tried - default_password and that doesn't work either.

nohart said:
Ya and I take the chance after spending hours re-installing the rom that it just gets encrypted again. Right now I have root and the phone is working fine. The only part as far as I can tell that is encrypted is the Internal Storage. The problem is that when I boot into TWRP it isn't asking for a password or my swipe pattern and if I go to the terminal in TWRP and type - twrp decrypt <your password> doesn't work either. I even tried - default_password and that doesn't work either.
Click to expand...
Click to collapse
Looks like a full wipe is in order. What ROM are you on?

ttocs99 said:
Looks like a full wipe is in order. What ROM are you on?
Click to expand...
Click to collapse
Evolution X V4 by - voidz777

exactly same thing happened to me too and i tried everything, stuck
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
there must be some way to fix this issue.

Permanently disable encryption when using custom ROMs

Hi, I have a question about encryption: I formatted data when installing a custom ROM. Now in TWRP, I have to enter my pattern to decrypt the phone.
a. This means my phone is encrypted, right?
b. Which .zip can I use for Disable Force Encryption?
c. Is there a way to force Disable Force Encryption now during the use of a custom ROM (I want to change to another ROM without formatting data, if possible).
Thx, tempe

tempe222 said:
Hi, I have a question about encryption: I formatted data when installing a custom ROM. Now in TWRP, I have to enter my pattern to decrypt the phone.
a. This means my phone is encrypted, right?
b. Which .zip can I use for Disable Force Encryption?
c. Is there a way to force Disable Force Encryption now during the use of a custom ROM (I want to change to another ROM without formatting data, if possible).
Thx, tempe
Click to expand...
Click to collapse
If you flash Orangefox recovery you can check Disable Force Encryption in settings -> OTA, so when you change ROM it automatically decrypt your phone everytime

Saluzzo97 said:
If you flash Orangefox recovery you can check Disable Force Encryption in settings -> OTA, so when you change ROM it automatically decrypt your phone everytime
Click to expand...
Click to collapse
Thanks. I'm on TWRP, though. Is there something similar as well?

Saluzzo97 said:
If you flash Orangefox recovery you can check Disable Force Encryption in settings -> OTA, so when you change ROM it automatically decrypt your phone everytime
Click to expand...
Click to collapse
Does that mean it actually disables encryption, or that it decrypts just before you flash system?

nikc0069 said:
Does that mean it actually disables encryption, or that it decrypts just before you flash system?
Click to expand...
Click to collapse
That's strange you want to disable encryption when your phone has a twrp installed.
That leads your phone to be like open book if you loose it!
I am sure you know what you are doing!
Cheers