I was using a ROM with Android 8.1 but decided to go back to a Nougat, based on the Stock ROM of my Samsung J7 Prime (SM-G610M), but after that I can no longer add any safe screen lock since the Settings closes after I enter the Pattern/Password, and this becomes an endless cycle. The strange thing is that this happens in any Stock-based ROM, does not matter if I wipe or any other thing, BUT in CM/LineageOS ROMs it works with no problems, which leads me to believe that it is a problem involving some partition of the phone because the wifi password is not getting saved after restarting the phone and after a clean flash of my Stock ROM through Odin the Stock Recovery says something like "cannot find /misc partition".
I'm attaching some logcat (extract the zip file, the logs are inside).
Please could anyone analyze them in order to find the cause/solution for this problem? I've tried everything but I can not solve it on my own.
Here are some of the things I've tried:
* Full wipe, including formatting /data and /system before each flash
* Install non-root and/or Gapps Stock-based required ROMs
* Encrypt and decrypt both the phone and the MicroSD card
* Change the kernel
* Install at least 6 different ROMs, based on Stock/TW ROMs
* In CM/LineageOS ROMs I have no problem whatsoever to add any secure screen locking method and I can use fingerprint and smart lock normally.
I've attached some other logs ins this thread too: https://forum.xda-developers.com/ga...-set-secure-screen-lock-t3827990#post77314466
After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.
SilentEYE said:
After losing all the data of my internal storage twice, I am searching for a final solution of this disaster.
If I let the phone encrypt everything, am I facing the problem of accessing it through twrp again?
Sometimes I just forget to install the decryption patch after each update.
Often I saw twrp asking me for a pattern, after an unwanted encryption. I couldn't enter a code like 6363 by swiping. --> data lost!
Any advice would be really appreciated.
Click to expand...
Click to collapse
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470
pingufanpoy said:
Fastboot and install the twrp with decryption support
Just rename it to recovery.zip before install
No need for passwords in twrp
FDE is optional when using this
https://www.androidfilehost.com/?w=files&flid=283470
Click to expand...
Click to collapse
I already had installed twrp with encryption support.
After flashing havoc rom the system started encrypting my internal storage.
TWRP was asking for encryption password, but there was none, because it was a clean flash.
The first time my system got encrypted ( maybe even deleted) was after upgrading to vendor / firmware v10.
Gesendet von meinem Redmi Note 4 mit Tapatalk
You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too
AntwnhsAnt said:
You need to flash Force encryption disabler zip every time you upgrade ROMs because on Pie encryption gets enabled on boot. Even if you decrypt using TWRP, if you flash another ROM it will still encrypt on boot if you don't flash FED.zip. I learned this the hard way too
Click to expand...
Click to collapse
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?
Uqbar said:
Sorry, but I don't get it.
At its very first boot, LOS encrypted my unencrypted phone without asking me for the key.
So I think it just chose a key at random (or maybe even an hardcoded one: who knows?).
How can this even work with (any) update?
What if I need to reboot my device? Will it reboot? (I don't dare to even test it).
I also run LOS on another phone (OP3T) which has asked me the encryption key when I chose to encrypt it.
So I see two main oddities with this phone:
LOS is encrypting MY OWN phone without asking me permission to do so and
LOS is failing to tell me which encryption key it's using, thus acting more like a bitlocker than as a security feature.
And I need a way to chose my very own encryption key, anyway. How to?
Click to expand...
Click to collapse
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.
Mooatreides said:
Its not LOS its the vendor/firmware flashed, everytime you put a new/vendor firmwar it "force encrypts" your phone on first boot. So used "disable force encryption" if you dont want it. Its just how it is so stop whining about "final solutions" for a disaster. Theres no disaster spen 10$ on an sd card and move your pictures or whatever there even while encrypted you can (keep it portable) then theres no problem.
Click to expand...
Click to collapse
I surely haven't fully understood this encryption thing.
Mainly because on one phone, the OP3T, it was done by the OS itself upon my request with my encryption key.
While on another one, the POCO F1, is being done by something else, the so called "vendor software".
I was willing to have encryption on the POCO F1, it looks like I cannot have it. Bare truth.
With LOS v16 on an OP3T, if I reboot to TWRP recovery (or system) and don't provide the key I defined myself, I won't get access to the storage.
With LOS v16 on a POCO, I can reboot to TWRP recovery (or system) and have the storage decrypted by the " vendor software" without providing any key.
So, to my very limited understanding at least, POCO F1 doesn't have encryption unless you are trying to access the storage from the bootloader or from a device which has been turned off!
Or am I missing something very important?
P.S.
I don't see how a uSD card would save me. Can I enable user controlled encryption on an uSD?
Hallo, i am Faiz.
I am a new user who moved from mi a1.
i've a quiestion, i want to install gcam in MIUI 10.3.3.0 instead of changing ROM (Now i used Evolution ROM). However twrp always asks the decryption password no matter what the version is it (tried with TWRP 0330, 1003/ 2003).
Tried format data but still, idk what to do.
Is any solution for this? or am i forgetting something?
Is there any Q rom that has
1. Safety Net passing without magisk
2. Supports encryption ( so that if I lose my phone, someone can't access data easily. Earlier P elms used to support encryption)
3. Selinux enforcing
Strangely a few months ago, there were many P roms that had all of the above, but I can't find Q roms that have these features. Is it something about Q. Also, even the recent update of Los 16 don't pass Safety Net. Has something changed about android/google that is causing it?
Thanks
Android Q has File based Encryption (FBE) not Full Disk encryption. And at present TWRP cannot decrypt FBE. And this it cannot Mount /data partition to do OTA updates or anything of the sort. The main TWRP maintainer is presently busy with other very important things in his life so FBE for TWRP may take a while.
Plus Xiaomi has not yet released Android 10 for Poco so it could also be that some firmware component is missing to support FBE (I'm not sure). If so it could be why the ROMs have trouble implementing it.
Regarding selinux, it will be a while before ROMs become really stable.
@ziglar24 if you're willing to learn you can contribute to twrp at Gerrit Code Review TWRP
Are there any members who have been able to encrypt a rooted Android Galaxy A8 (SM-A530F) with Android Pie. Or at least with an Android phone running Android Pie? I would be very interested to know how you did it? Rooting was straight forward but root with encryption so far has been unsuccessful.
I have tried suggestions from the following forum posts, with no luck:
https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Regarding encryption, can anyone recommend any other good encryption alternatives that I could use instead of full device encryption? For example an encryption solution that will encrypt all personal data or a mounted encrypted home folder(similar to Linux) where all personal information can reside and be encrypted.
Any good encryption apps? I see that there are many in the play store, but which one, are they any good?
Grateful for any help/suggestions. Thanks.