Hello, has anyone succesfully disabled force encryption on XIAOMI.EU rom? I'm installing it now and rooting, but it would be nice to have option to backup phone memory or change something in it in recovery, when recovery will be available. What should i do to disable encryption, are there any disadvantages other than poorer privacy when disabling it?
Related
I use a Redmi Note 4 Snapdragon variant. When I try to install a ROM and set it up, system ui force closes at the add fingerprint screen.
This issue is present on Atomic OS and Citrus CAF. Only AOSP extended works properly.
I have tried beans and opengapps.
I tried latest firmware and an older one, it doesn't affect behaviour.
If i skip setup and set up as new instead of restore from cloud backup, it works fine; but i really need to restore as there are a lot of WiFi passwords and such that i need.
Can anyone guide me?
Try deleting settings's cache. It may help.
Hi, All -- I'm trying to disable forced encryption on my Nexus 9 running stock Android 7.1.1 N4F27O. And I can't find materials to execute any of the instructions I'm seeing online: I don't see a boot_noforceencrypt.img kernel for N4F27O (which is required for these instructions), and neither WugFresh's Nexus Root Toolkit nor SkipSoft seem to have been updated with N4F27O. Can anyone help me figure out what I need to do?
Thanks!
Alan
Format data and : -
To avoid encryption, you would need to flash an additional zip to avoid it.
SuperSU, Magisk, Custom Kernel or FED Patcher can prevent it.
If you have TWRP, you have to format data (not just wipe) and flash either fed patcher V8, SuperSU, or magisk to disable forced encryption.
Im on latest stable MIUI 9 the problem is when I go to Settings > Storage, settings stops working. Tried wipeing dalvik and cache from twrp
Immortal0907 said:
Im on latest stable MIUI 9 the problem is when I go to Settings > Storage, settings stops working. Tried wipeing dalvik and cache from twrp
Click to expand...
Click to collapse
Can you be a bit more specific? Try answering the following question so that I can be helpful.
Which build of MIUI9 did you flash?
Which recovery did you use?
Did you flash OpenGapps package on the top of it?
Is it a custom MIUI that you use?
Most probable cause of this would be flashing a bigger OpenGapps package (stock or above) after flashing MIUI. OpenGapps tries to replace the stock MIUI applications with same application signature and hence causes incompatibility with the MIUI ecosystem. Hence, you face force-closes. The other reason might be the use of an incompatible third-party theme that does not render the Settings app properly. Just possibilities.
ADInfinity1999 said:
Can you be a bit more specific? Try answering the following question so that I can be helpful.
Which build of MIUI9 did you flash?
Which recovery did you use?
Did you flash OpenGapps package on the top of it?
Is it a custom MIUI that you use?
Most probable cause of this would be flashing a bigger OpenGapps package (stock or above) after flashing MIUI. OpenGapps tries to replace the stock MIUI applications with same application signature and hence causes incompatibility with the MIUI ecosystem. Hence, you face force-closes. The other reason might be the use of an incompatible third-party theme that does not render the Settings app properly. Just possibilities.
Click to expand...
Click to collapse
MIUI 9 latest global stable build. 9.6.2 redmi note 4 SD
TWRP Recovery
No i didnt flash gapps they are alredy in MIUI?
Its not custom miui, downloaded it from their site and flashed with mi flash. Im running magisk , camera2 api enabler module and viper4android. Everything is working great except that settings force close. Silly thing is ive been using this rom for like a month and didnt go into Storage... I just noticed that force close.
Immortal0907 said:
MIUI 9 latest global stable build. 9.6.2 redmi note 4 SD
TWRP Recovery
No i didnt flash gapps they are alredy in MIUI?
Its not custom miui, downloaded it from their site and flashed with mi flash. Im running magisk , camera2 api enabler module and viper4android. Everything is working great except that settings force close. Silly thing is ive been using this rom for like a month and didnt go into Storage... I just noticed that force close.
Click to expand...
Click to collapse
Oh I see. Have you tried disabling any of the magisk module and check whether that improves the condition? Force close while going into storage might actually mean something. How about you go to applications settings in Settings app and clear data and cache of storage manager app? This might actually work, you know. Let me know about that.
Solved it thanks for help. Issue was being cause by Face ID for RN4 module which I forgot to mention. I disabled it and it just works.
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?
I've been out of the Android scene for a while so it's the first time I'm seeing this forced encryption. Do I need to disable forced encryption to flash and install magisk?
Also why do people disable encryption? Isn't encryption a good thing?
Android Treble enabled devices will have force encryption enabled and also DM Verity check enabled.
DM verity does not allow an Android system to boot if the system integrity has changed or in simple words, if some of the system partitions are changes such as: boot, recovery, system partition etc.
In order to flash a TWRP recovery by replacing the stock recovery you need to disable DM verity and disable force encryption.
This zip file is TWRP flashable which disables the Force Encryption on Android phone with Treble enabled.
Click to expand...
Click to collapse
link :good: