I recently unlocked the bootloader and rooted my Moto G Power.
I noticed in Magisk that Preserve DM Verity and Preserve Forced Encryption were both checked. They were not checked on my old LG V20.
I know on my old device, encryption messed with TWRP, which is why it was disabled.
But encryption IS enabled on the Moto G Power. I've heard that the encryption can put a dent in performance.
Aside from that, is there any reason why I should keep or disable encryption?
And while "Preserve Forced Encryption" is pretty obvious, can someone explain "Preserve AVB 2.0/dm-verity"? (AVB is Android Verified Boot, so maybe I should leave that enabled?)
Thanks in advance!
A bit of an old post, but while the v20 guys are doing what they're doing with their cursed LG phones that won't stop ****ing dying that also apparently have impossible encryption, the moto g8 bois have figured out the encryption on the very first release of TWRP 3.4.0.0
Theres no real hit to performance at this point for this device, also it doesn't make a difference in backups as TWRP is made to handle encrypting/decrypting now (although I've had problems with backup/restore altogether on this phone I guess since its not officially supported) but theres no real reason to disable it, its a good layer of security if you ever lose your phone or the cops get a hold of it.
Related
(Verizon HTC One M9, S-OFF, bootloader *** UNLOCKED ***, Software status: Official, TWRP recovery installed, Android version 5.0.2, HTC Sense version 7.0 Software number 1.33.605.15)
I'm anticipating a requirement in my near future to turn on "Phone storage encryption (Protect content on this phone with a password)" under Settings -> Security. When I did this under similar circumstances on my HTC One M7, it seemed to adversely affect the performance of the phone. I encountered a lot of random freezes at various points (after entering my unlock PIN, waking up the phone, switching apps, even occasionally during phone calls).
In fairness, I had a lot of stuff on internal storage on my old phone - pictures, audio, etc. - that I now store on my 32GB microSD card on the M9. Nonetheless, the prospect of encrypting my internal storage is intimidating, especially because it's apparently a one-way operation, and there's No Going Back if the phone performance starts to lag as the old phone's did.
Has anyone else experienced any similar troubles after turning on Phone storage encryption? Also, I'm not averse to moving off of the HTC stock ROM; I just haven't done it yet. Is there a particular ROM that seems to perform better -- or worse -- with encrypted internal storage?
Thanks.
Good question and I realy would like to join in.
Normaly Google says, since Android 5 Storage encryption should be standard and phones with native Android 5 should have hardware accelerated encryption. But there is no information thats says which phone have this hardware accelerated encryption.
And in addition most phones with native android 5 don't have standard encryption activated.
So is there anyone who tested the M9 with storage ecryption?
\Edit:
This article says AES comes with ARMv8 wich is used in Snapdragon 810 http://www.chip.de/news/Rueckzieher...sselung-in-Android-5.0-Lollipop_76997991.html
encryption disabled dial pad and texting
I have a sprint M9, twrp recovery, rooted, and flashed Viperone ROM.
Everything was working great.
Because of work email needs and the need for Microsoft Exchange, I had to encrypt the phone. So I did.
After encryption, I cannot make outbound calls. I receive calls. Just cannot dial them. Seems like the problem is with the dial pad. Lets me enter the number, but when I hit "call" it just goes away. I cannot type internal phone commands like ##1234## to get information. Just disappears.
Also, I cannot send or receive text messages.
I went into TWRP to revert back to my backup. And of course no backup is there. Everything is encrypted and unreadable by TWRP. I have read a lot on these boards and thank you. I cannot find much written on this subject.
Sprint reports everything is fine and working on their end.
So frustrated. Seems like an easy setting or fix. The dial pad is not reading something from an encrypted file?
Sorry for the ignorant language. I am very new at all this. Any ideas?
crk53 said:
I have a sprint M9, twrp recovery, rooted, and flashed Viperone ROM.
Everything was working great.
Because of work email needs and the need for Microsoft Exchange, I had to encrypt the phone. So I did.
After encryption, I cannot make outbound calls. I receive calls. Just cannot dial them. Seems like the problem is with the dial pad. Lets me enter the number, but when I hit "call" it just goes away. I cannot type internal phone commands like ##1234## to get information. Just disappears.
Also, I cannot send or receive text messages.
I went into TWRP to revert back to my backup. And of course no backup is there. Everything is encrypted and unreadable by TWRP. I have read a lot on these boards and thank you. I cannot find much written on this subject.
Sprint reports everything is fine and working on their end.
So frustrated. Seems like an easy setting or fix. The dial pad is not reading something from an encrypted file?
Sorry for the ignorant language. I am very new at all this. Any ideas?
Click to expand...
Click to collapse
Hi
I know this is late on this thread, but I was wondering if and or how you resolved your dilemma? I'm considering encrypting my HTC m9 on 6.0
DGL2033 said:
Hi
I know this is late on this thread, but I was wondering if and or how you resolved your dilemma? I'm considering encrypting my HTC m9 on 6.0
Click to expand...
Click to collapse
HTC uses proprietary (non-AOSP) encryption. As a result, TWRP won't be able to decrypt your phone if you have encrypted it on a stock or stock-based ROM.
In theory, TWRP can decrypt when encryption is performed with an AOSP ROM (CyanogenMod, CandySiX, et cetera). Unfortunately, encryption - though functional - doesn't behave as expected even on these ROMs. Your phone will indeed be encrypted successfully, but some ROMs (CyanogenMod) won't re-boot after encryption and other ROMs will boot (CandySiX) but still not be decrypted by TWRP.
TLDR: If you want encryption, go for it but know that you're locked into that choice.
computerslayer said:
HTC uses proprietary (non-AOSP) encryption. As a result, TWRP won't be able to decrypt your phone if you have encrypted it on a stock or stock-based ROM.
In theory, TWRP can decrypt when encryption is performed with an AOSP ROM (CyanogenMod, CandySiX, et cetera). Unfortunately, encryption - though functional - doesn't behave as expected even on these ROMs. Your phone will indeed be encrypted successfully, but some ROMs (CyanogenMod) won't re-boot after encryption and other ROMs will boot (CandySiX) but still not be decrypted by TWRP.
TLDR: If you want encryption, go for it but know that you're locked into that choice.
Click to expand...
Click to collapse
Hey, thanks for the quick, informative reply. I may just hold off for now, as I'm likely to root after warranty is up. But,FYI, From what I read in the HTC user guide, I could undo the HTC encryption with a factory reset, which I would probably do when they stop updating, and I move to CM or other ROM at that point. I appreciate the advice greatly, as it sounds like personal experience, or you're well informed on the subject, or both.
DGL2033 said:
Hey, thanks for the quick, informative reply. I may just hold off for now, as I'm likely to root after warranty is up. But,FYI, From what I read in the HTC user guide, I could undo the HTC encryption with a factory reset, which I would probably do when they stop updating, and I move to CM or other ROM at that point. I appreciate the advice greatly, as it sounds like personal experience, or you're well informed on the subject, or both.
Click to expand...
Click to collapse
My pleasure!
To confirm, yes you can absolutely remove encryption via factory reset.
On my U11 (Oreo 8.0/currently stuck on ViperU2.1 as nothing else seems to boot) I can't seem to decrypt my device (its lagging a bit due to encryption I believe.)
It won't allow me to decrypt in Settings, nor will it decrypt on a hard reset, nor allow me to change it after a hard reset. And reflashing Viper still has phone encrypted.
Any tips?
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
I'm also interested in this. So bump for a more knowledgeable member to comment.
I think this thread proved pretty conclusively that there is no real world performance benefit in decrypting.
I activated file encryption on my N5X, specifically to allow for direct boot. I had N with full disk encryption on my N5X for about 72 hours before switching. I see no performance difference -- it was smooth before, and it is smooth now.
rockhardy said:
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
Click to expand...
Click to collapse
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Thanks for your comment.
In that case i think i will be switching to File-based encryption to enjoy direct boot feature.
sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
ABSathe said:
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
Click to expand...
Click to collapse
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try. If it does help, it will probably be coincidence because you had to format user partition to decrypt your phone which is equivalent of factory reset.
sfhub said:
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try.
Click to expand...
Click to collapse
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
ABSathe said:
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
Click to expand...
Click to collapse
Before you do factory reset, I suggest you get rid of any pin/pattern/password you might have configured. This will disable the factory reset protection, just to be on safe side.
You can do it from android.
If you say this problem was there from beginning, then it probably migrated over from existing account restoration of apps. You might want to try installing onto a new google account to test that theory out. The install a couple of apps at a time while verifying everything remains stable.
Hi,
Do folks think that switching to File Based Encryption might help avoid this issue - a decryption failure on reboot with Factory Reset the only solution? My phone is 13 months old and now out of warranty and this has happened 5 times to date - once about 6 months ago, once about 3 months ago and then worryingly 3 times in the last month. Stock unmodified on 7.1.1
Hey, When will TWRP support this? I've been waiting for ages.....
So I kind of like the fact encryption is turned on automatically by Nextbit (and I did figure out how to get out of my encryption loop)
And I have tried to encrypt the disk with
-Pacman ROM
-Reserrection ROM
-Paranoid Android
and all of them bootloop and never actuall boot up once you press "encrypt".... so is it impossible to encrypt once you have an unlocked bootloader and recovery installed? I get its detrimental to the whole process of flashing incessantly but still
Grrrrrrr
Can sum1 confirm
tlxxxsracer said:
If you unlock the bootloader,that alone won't cause encryption issues. You have to flash a specific boot.img or zip that will disable encryption.
Don't unencrypt and should be fine.
Not sure why you'd want to encrypt if your BL is unlocked. Encryption only hurts performance
Click to expand...
Click to collapse
thanks for the reply
I wanted to encrypt my current ROM to just get the extra protection from theft or lost device.
I really like the current ROM im using and dont need to flash anymore currentlty, so i would be fine locking it down with encryption
But i cant get ANY of the ROMS to encrypt like they normally do say compared to the G3
So there is a solution to this. Basically, when you encrypt the file system on one rom, even when you wipe the data certain things are still tied to the old file system. That's why when you go to encrypt the encryption fails, because the remnant stuff from the other rom is in the way. The solution is to completely reformat the data partition (using TWRP, select format data, or change the data file system to F2FS and then back to ext4.). This will clear the conflicts causing encryption to bootloop. However, this process will need to be repeated every single time you switch roms (updating a rom is fine).
I believe Cyanogenmod supports encryption, though I have never tried it.
yanowman said:
So I kind of like the fact encryption is turned on automatically by Nextbit (and I did figure out how to get out of my encryption loop)
And I have tried to encrypt the disk with
-Pacman ROM
-Reserrection ROM
-Paranoid Android
and all of them bootloop and never actuall boot up once you press "encrypt".... so is it impossible to encrypt once you have an unlocked bootloader and recovery installed? I get its detrimental to the whole process of flashing incessantly but still
Click to expand...
Click to collapse
If you flashed the custom boot image, you CANNOT re encrypt your phone. Won't work.
Hi,
I have a LG G4 and use the stock ROM but want to get rid of google's observation and bloatware. I am looking for a custom ROM that focuses on privacy and runs stable on the LG G4.
It must
- be usable without Google
- provide a working full-phone encryption + SD card encryption like the stock ROM does
- provide fast updates (my stock rom has security level january 17 which is ridiculous)
I already tried LineageOS with the newest version and it worked well with one exception: I could not encrypt my phone. I tried it several times but I either got into a boot loop or Lineage OS booted but all my preferences and apps were lost (like I did a factory reset, but I didn't). When I then started TWRP recovery it asked me for my password and declined it altough it was 100% correct. The only possibility was to wipe all data and install LineageOS again. Very strange: I could also "encrypt" my phone without providing a PIN, password or something else. I would expect an error message to be displayed but there was none.
I also tried Ressurection Remix but the encryption failed as well (boot loop after encryption finished).
Could it be that TWRP causes these problems? Has anyone successfully intalled a custom ROM and encrypted the LG G4? Maybe another ROM? I am very open for new suggestions
For now I had to reinstall the stock ROM because that's the only way I can encrypt my phone...
Regards
maasG4
Does nobody care for encryption?
1984 is real, how can somebody just don't care?
How can encryption protect your privacy?
But you can use stock rom too.
Just reset phone, set it up without google account (you have to delete the accout before resetting fyi)
root it, use afwall and jdisable the common lg and google stuff.
Use floss open source apps from froid.
Thats it.
If you want to use stuff like network location without gapps the you have to use LOS. If you want more google stuff without google you have to use crdroid rom.
But I already tried and its a pain on the ass.
Lol yes encryption is something where many people say it's completely useless! I love those discussions where people say why do you care about encryption? Well it's their fault not mine I encrypt everything and always that's why I build TWRP with decryption support because no one else cares.
I use RR marshmallow plus FDE but I am about to switch to LOS 13 because of the security patches inside
Iirc (it's more than 1 year ago) it was a little bit tricky to set up because as you already noted nobody cares about encryption! everything like rooting or custom ROMs have all one thing in mind disable encryption and that's what's happening when you install root or when you use a custom ROM normally.
If you can wait until I have switched to LOS I could tell you more but I have no time frame for this so if you don't want to wait you should investigate the fstab file and if you're using Super su the installer scripts as well
.
Sent from my LG-H815 using XDA Labs
maasG4 said:
Hi,
I have a LG G4 and use the stock ROM but want to get rid of google's observation and bloatware. I am looking for a custom ROM that focuses on privacy and runs stable on the LG G4.
It must
- be usable without Google
- provide a working full-phone encryption + SD card encryption like the stock ROM does
- provide fast updates (my stock rom has security level january 17 which is ridiculous)
I already tried LineageOS with the newest version and it worked well with one exception: I could not encrypt my phone. I tried it several times but I either got into a boot loop or Lineage OS booted but all my preferences and apps were lost (like I did a factory reset, but I didn't). When I then started TWRP recovery it asked me for my password and declined it altough it was 100% correct. The only possibility was to wipe all data and install LineageOS again. Very strange: I could also "encrypt" my phone without providing a PIN, password or something else. I would expect an error message to be displayed but there was none.
I also tried Ressurection Remix but the encryption failed as well (boot loop after encryption finished).
Could it be that TWRP causes these problems? Has anyone successfully intalled a custom ROM and encrypted the LG G4? Maybe another ROM? I am very open for new suggestions
For now I had to reinstall the stock ROM because that's the only way I can encrypt my phone...
Regards
maasG4
Click to expand...
Click to collapse
Only one name in cellular phone is black phone 2 it uses military type encryption and if you lose it you can call up and make it explode........ Lol
Updates Mid 2018
Hi,
as I had no success last year when I wrote this post, I lost it out of sight. Now I would like to give it another try.
Unfortunately I cannot find any custom ROM with a current version that also supports LG G4. LineageOS supports a lot of phones but no G4, the same for RR OS.
Is there another alternative that officially supports LG G4 and also works with encryption?
If not, I think it is time to move from my loved G4 to another phone. I do not feel comfortable with a phone that got no updates for almost two years. This time, I would directly focus on finding a phone that gets regular updates (like the new Nokias, as far as I know) or has good support for custom ROMs (like Nexus/Pixel). Are there any suggestions for a phone that is comparable to my G4 (I especially love the camera) but supports current custom ROMs or has regular updates from the manufacturer?
Looking forward to any recommendations!
steadfasterX said:
If you can wait until I have switched to LOS I could tell you more but I have no time frame for this so if you don't want to wait you should investigate the fstab file and if you're using Super su the installer scripts as well
Click to expand...
Click to collapse
Have you already tried it?
Thanks!
maasG4 said:
Hi,
as I had no success last year when I wrote this post, I lost it out of sight. Now I would like to give it another try.
Unfortunately I cannot find any custom ROM with a current version that also supports LG G4. LineageOS supports a lot of phones but no G4, the same for RR OS.
Is there another alternative that officially supports LG G4 and also works with encryption?
If not, I think it is time to move from my loved G4 to another phone. I do not feel comfortable with a phone that got no updates for almost two years. This time, I would directly focus on finding a phone that gets regular updates (like the new Nokias, as far as I know) or has good support for custom ROMs (like Nexus/Pixel). Are there any suggestions for a phone that is comparable to my G4 (I especially love the camera) but supports current custom ROMs or has regular updates from the manufacturer?
Looking forward to any recommendations!
Have you already tried it?
Thanks!
Click to expand...
Click to collapse
Officially - cypher os supports your G4
Unofficially (but maintained by myself, @steadfasterX and @kessaras) you can choose from LineageOS, AICP, Cypher (newer versions with more patches - @kessaras is also the official Cypher maintainer so no difference there) and RR
Anything Oreo supports encryption - anything nougat doesn't
However, Oreo has a bug with BT calling - Calling through a BT headset doesn't work
Hi,
I'm wondering if using encryption has any use (especially on a fully untouched stock phone).
A fully untouched stock phone has a locked bootloader so no-one can install a custom recovery and access the files and when it's on you need to unlock it before you have access. Why to use encryption then?
My phone is rooted and so has twrp.
I'm wondering now since it's no problem for twrp to bypass default encryption couldn't do anyone else the same then on an untouched but encrypted phone too?
So for my phone I think having default encryption is equally secure as having no encryption at all, that's why I used my password for encryption (what I accidentally replayed with the default 2 days ago).
And at last, where is the difference between the default encryption and the one with a custom password?
An article said with encryption booting the system can be up to 50% as slow as normal boot and with my custom encryption password that was the case. However, since I'm on default encryption now again it boots as fast as it did without encryption on nougat. That makes me wonder a bit what that default encryption really is and which use it has.
Greetings, 7080