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.
Hello everyone!
I am wondering how to enable encryption of my P9 Lite running Nougat B370. My phone is rooted, bootloader unlocked and TWRP installed, if that is relevant.
In the menus I don't find any option to encrypt my phone. So, anyone knows if it is possible?
If you mean data encryption, it is already encrypted.
Potato997 said:
If you mean data encryption, it is already encrypted.
Click to expand...
Click to collapse
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?
android_xpert said:
You sure about that? Because TWRP can access my data partition without pin...
Is there any way to check whether disk encryption is truly enabled?
Click to expand...
Click to collapse
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.
bghyt said:
It's encrypted unless you unencrypted it with twrp but the latest update of twrp (nouget) lets you backup data unlike twrp on MM.
Click to expand...
Click to collapse
It's strange though, I've never unencrypted my phone with twrp. But when I boot into twrp my whole data partition is open for access without any sort of password/pin. Seems to me there is no encryption active.
TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.
Potato997 said:
TWRP can mount data partition, but it does not mean that it is able to decrypt it.
It can backup/restore or format it which is what usually what a TWRP do, if you install a custom ROM like LOS you will need to format it because the system can't decrypt it while stock ROM can do it.
Click to expand...
Click to collapse
What I meant by my post is not only that twrp can mount the data partition. I can also access all my files within said data partition.
Hi, ive been wondering why all those roms folks put out are unable to encrypt the /data partition.
Any rom i tried so far is soft rebooting after i invoked the encryption option. No encyption happening at all.
And if i do it manually via adb shell > su # vdc cryptfs enablecrypto wipe password somethingpw
I sort of soft brick the device boot until i whipe the data partion via twrp.
Thereof i am wondering why its broken in the first place and if theres a chance if folk will fix this over time or any 3rd Party Roms will be stuck w/o a chance to encrypt personal data.
Myau said:
Hi, ive been wondering why all those roms folks put out are unable to encrypt the /data partition.
Any rom i tried so far is soft rebooting after i invoked the encryption option. No encyption happening at all.
And if i do it manually via adb shell > su # vdc cryptfs enablecrypto wipe password somethingpw
I sort of soft brick the device boot until i whipe the data partion via twrp.
Thereof i am wondering why its broken in the first place and if theres a chance if folk will fix this over time or any 3rd Party Roms will be stuck w/o a chance to encrypt personal data.
Click to expand...
Click to collapse
I was facing issues with my LOS 15.1, afaik unencrypted. Then I flash stock Oreo Feb using Mi Flash tool, with option 'clean all and lock'. Then I root it with magisk and flash LOS 15.1. The next thing I know, my phone is encrypted
kopitalk said:
I was facing issues with my LOS 15.1, afaik unencrypted. Then I flash stock Oreo Feb using Mi Flash tool, with option 'clean all and lock'. Then I root it with magisk and flash LOS 15.1. The next thing I know, my phone is encrypted
Click to expand...
Click to collapse
Did you dirty flash or whipe the installed OS?
Myau said:
Did you dirty flash or whipe the installed OS?
Click to expand...
Click to collapse
Clean install, i.e. wipe all.
kopitalk said:
Clean install, i.e. wipe all.
Click to expand...
Click to collapse
Thank You, for confirming that Encryption works, i was almost at the verge of returning the phone.
Got it to work now.
....
The tldr of all i tested and messed around with is:
If you whipe Data trough twrp, with the special dialog where you have to type in YES. which folk reccomend to use to remove encryption,
will mean you brick the encryption and requires a re-flashing of the stock rom.
Secondly if you only go into advanced whipe, Art, System and data and then install a rom, it should say 'decrypted with default password'
Which is a dead give away that encryption might going to work just fine, rebooted into bootloader w/o into system, installed gapps pico, (eeh) and magisk, which also mentioned something about encryption as the log ran trough. Then rebooted into system, and now it says encrypted. And i can set up a boot pin/password before it fully boots. GREAT!
Soo.... If it says decrypted and won't encrypt, you have to flash stock, check its encrypted. Then install costum rom without removing encryption.
Once you removed it, its back to stock rom for new a /data setup/encryption.
Ok have a ZTE Axon 7 can't flash any thing because of it instantly encryption and I get recovery and then game over any one have a Cure for this......... thanks in advance.
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
chairmanmarv said:
You have to do a factory wipe, to remove encryption. Then when setting up the phone again when it prompts you to set a security pin or finger sprints skip that part.
Click to expand...
Click to collapse
Tried that and it didn't work.....it doesn't matter what I flash stock ROMs tell me my password is correct but memory is corrupt and need to be wiped and when I flash a custom ROM it doesn't boot just two flashes of the led and that's it.
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Just found out that the phone has bricked itself it would play any video or sound so did a hard reset now just getting a constant boot loop trying to get it in to EDL as we speak.....got EDL flashed stock ROM in miflasher now stuck on splash screen.......been on the splash screen for 10 minutes now.......
chairmanmarv said:
Which TWRP recovery are you on?
What I mean by Factory reset is a full Factory wipe your whole internal is erased. It is like a clean slate new phone.
You should have all the necessary files for your flash on your sd card there is an option to select storage to flash from there.
So when I first swapped from Stock Nougat to AEX I was encrypted on 5/4 ROM my internal was locked by encryption and could only dirty flash roms. it was annoying so I factory wiped and flashed latest AEX from there and didn't set up security right away so no encryption.
I realised my TIBU back ups were all on internal so had to basically start from scratch oops lol.
It is a little outdated now with the official Oreo roms but user @Oki 's guide helped me a lot and has clear steps and guides to get you all rooted and sorted on custom roms.
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Click to expand...
Click to collapse
Ok now got the thing back was able to reunlock the bootloader and installed recovery flashed candy rom with one issue could not mount system so now just flashed Oreo stock rom so all good again....... thanks for the help
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
AnonVendetta said:
The stock ROM encrypts by default, and formatting data partition in twrp is the only way to remove it. But to prevent the encryption before it happens, you have a few options:
1. If you dont plan to root, flash @jcadduono's no verity opt encrypt zip (Google it)
2. Magisk and SuperSU can optionally disable encryption before it happens. Magisk Manager has a config option if you're installing from the app. You can use Aroma SuperSU config if SuperSU is your root method of choice.
Hope that helped!
I would like to note that AOSP/Lineage/CM-based ROMs dont encrypt by default. though Im sure it could be enabled if you wanted to. This seems to be unique to the stock ROMs, mainly because Google insists that phone OEMs should go for higher security by enabling encryption as the default.
Click to expand...
Click to collapse
Yep this is the problem I am having now....... can't find much info about it.
Just updated to Oreo December patch. Is it true no-verity-opt-encrypt-5.1 is no longer needed before Magisk for rooting? I vaguely recall reading something like it.
Also, is factory wipe after TWRP before Magisk really needed?
I wish I wrote down the process from the last update. Angry at myself for forgetting.
goodjuju said:
Just updated to Oreo December patch. Is it true no-verity-opt-encrypt-5.1 is no longer needed before Magisk for rooting? I vaguely recall reading something like it.
Also, is factory wipe after TWRP before Magisk really needed?
I wish I wrote down the process from the last update. Angry at myself for forgetting.
Click to expand...
Click to collapse
Depends on if you want your data partition encrypted or not.
By default the device is encrypted or will encrypt data after flashing fastboot firmware. If you want the partition to be decrypted format data after installing TWRP and flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip after that. Boot your device, reboot to TWRP and flash latest magisk (18).
Normally Magisk itself should prevent the re-encryption but in my case that didn't happen.
A factory reset is not necessary but formatting data will erase your internal storage.
Wolfcity said:
Depends on if you want your data partition encrypted or not.
By default the device is encrypted or will encrypt data after flashing fastboot firmware. If you want the partition to be decrypted format data after installing TWRP and flash Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip after that. Boot your device, reboot to TWRP and flash latest magisk (18).
Normally Magisk itself should prevent the re-encryption but in my case that didn't happen.
A factory reset is not necessary but formatting data will erase your internal storage.
Click to expand...
Click to collapse
Thanks Wolfcity. I will leave the partition encrypted. I am writing down a step by step OTA process including my personal tweaks this time! No more relying on my memory and posting silly questions.