Develop Bugs

Why disable encryption?

I have seen several posts referring to disabling encryption but not a reason why I should. I am rooted, running 6.0.1, and I skipped the decryption step during the root. My phone says it is encrypted. I haven't noticed any lag but I have only had my phone for 1.5 weeks. One would "assume" that having it encrypted would be better. So why would I want to disable it? Is there a cumulative effect that I don't know about?
Thank you.

If you don't want to and you want to leave it encrypted go for it. An encrypted fs will have slower read/write speeds, and some people aren't worried about having their phone encrypted. You can always re encrypt in security settings just now you wont be forced to have it on.

For my personal device i never use encryption, without it devices are notably faster for me.

67p912 said:
I have seen several posts referring to disabling encryption but not a reason why I should. I am rooted, running 6.0.1, and I skipped the decryption step during the root. My phone says it is encrypted. I haven't noticed any lag but I have only had my phone for 1.5 weeks. One would "assume" that having it encrypted would be better. So why would I want to disable it? Is there a cumulative effect that I don't know about?
Thank you.
Click to expand...
Click to collapse
It's more convenient for flashing ROMs if it's decrypted. Because TWRP recovery can't see an encrypted partition, you can't download a ROM to your phone's storage and then flash it in recovery. It would be nice if we could have two data partitions, an encrypted one and an unencrypted one.

Jacquestrapp said:
It's more convenient for flashing ROMs if it's decrypted. Because TWRP recovery can't see an encrypted partition, you can't download a ROM to your phone's storage and then flash it in recovery. It would be nice if we could have two data partitions, an encrypted one and an unencrypted one.
Click to expand...
Click to collapse
TWRP has be able to 'see' encrypted storage for a while now.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
TWRP has be able to 'see' encrypted storage for a while now.
Click to expand...
Click to collapse
Is there some kind of trick to that, or some setting in TWRP that needs to be enabled? It didn't work for me the first time I tried it.

Jacquestrapp said:
Is there some kind of trick to that, or some setting in TWRP that needs to be enabled? It didn't work for me the first time I tried it.
Click to expand...
Click to collapse
It just works and has since November with TWRP version 2.8.7.2.
Sent from my Nexus 5X using Tapatalk

Regarding encryption, if I were to do a twrp backup with 'encryption on', can i restore that backup on a 'encryption off' phone after.
My plan is to:
Nandroid backup with encryption on
Decrypt (which erases all user data)
Restore backup
How will this affect the backup since 1 has encryption on previously?

how to disable encryption?

cavalloz said:
how to disable encryption?
Click to expand...
Click to collapse
Code:
fastboot format userdata
^^^This will wipe your internal storage^^^
Edit: Need a modified kernel that doesn't force encryption.

How about a few more details on turning off encryption please.
Sent from my Nexus 5X using Tapatalk

Decrypting Storage

I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?

I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/

Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/

cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.

Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387

blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.

Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs

MIUI 9 encryption

Hi guys,
I'm trying to find ROM that supports encryption. There are two options available:
1. Encrypt using lock screen password
2. Encrypt device
The first one does nothing. I tried booting into TWRP and see all files unencrypted that are supposed to be, according to the disclaimer.
The second does not finish, it just gets to 100% and then stuck (I waited for a few hours) and the only way it to reboot having corrupted FS.
So the question is how to enable data encryption?
I tried almost everything global stable, Chinese stable and dev ROMS, original and miuipro and xioami.eu. And everything with the same outcome.

MIUI should be using file based encryption which will be present when you boot the ROM.
No need to enable it. Just don't disable it....
Most of the Nougat ROMs for Mi 6 support file based encryption now so all you need do is FORMAT data (not just wipe) and it will be present.
My suggestion would be to install and MIUI stock ROM and then format data (that includes internal storage so backup if you are using it now).
Then reboot and start phone as clean device.
There doesn't seem to be an advantage to using ROMs that don't have file based encryption and then trying to enable it later.
Rom either has FBE or it doesn't have encryption at all for me :/

Does it work for you? How do you confirm this?
I did format from TWRP, ran through setup and took a photo.
I still can access files and can see the content without entering any password from TWRP.
By default all encryption options are unset in MIUI.
You are saying right things if that would be vanilla Android but it seems something is broken in MIUI.

conmu said:
Hi guys,
I'm trying to find ROM that supports encryption. There are two options available....
.
Click to expand...
Click to collapse
I flashed last global stable rom (1.9Gb .tgz) using mi flash tool after a format data in twrp and the device was encrypted by default. I only had to switch on "encrypt using lockscreen password" in privacy settings. But i don't know why even though i flash twrp the stock recovery returns after every reboot
Usefull link:
https://gadgets.ndtv.com/mobiles/fe...nstall-redmi-note-4-mi-max-2-6-5s-mix-1771733

valeriopastore20 said:
I flashed last global stable rom (1.9Gb .tgz) using mi flash tool after a format data in twrp and the device was encrypted by default. I only had to switch on "encrypt using lockscreen password" in privacy settings. But i don't know why even though i flash twrp the stock recovery returns after every reboot
Usefull link:
https://gadgets.ndtv.com/mobiles/fe...nstall-redmi-note-4-mi-max-2-6-5s-mix-1771733
Click to expand...
Click to collapse
You have to disable the stock recovery being reflashed from system with a script.
Not sure where you get that though it comes default with Coffaces TWRP.
Are you using the official TWRP?
If so does it work properly?

Dobsgw said:
You have to disable the stock recovery being reflashed from system with a script.
Not sure where you get that though it comes default with Coffaces TWRP.
Are you using the official TWRP?
If so does it work properly?
Click to expand...
Click to collapse
I'm using this one
https://forum.xda-developers.com/mi-6/development/recovery-twrp-3-1-1-0-xiaomi-mi6-t3608008
because with other recoveries i had problems while restoring data from backup (error 255).

valeriopastore20 said:
I'm using this one
https://forum.xda-developers.com/mi-6/development/recovery-twrp-3-1-1-0-xiaomi-mi6-t3608008
because with other recoveries i had problems while restoring data from backup (error 255).
Click to expand...
Click to collapse
Okay cool.
Doesn't look like it has decryption support so maybe I'll try official

valeriopastore20 said:
the device was encrypted by default
Click to expand...
Click to collapse
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?

conmu said:
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?
Click to expand...
Click to collapse
Settings - security - encryption = "phone encrypted"

conmu said:
Sorry for the stupid question but how did you understand this? What is the actual check to confirm this?
Click to expand...
Click to collapse
in privacy settings you will see something like this (i don't have miui9 encrypted anymore so i looked for a screenshot on google) http://attach.en.miui.com/forum/201604/10/202340xmpnzcaciianqnpg.png

Dobsgw said:
Settings - security - encryption = "phone encrypted"
Click to expand...
Click to collapse
SYSTEM & DEVICE > Additional settings > Privacy: Advanced # Encrypt phone
If this it then that is point #2 from my initial message and that never finishes with any ROM I tried
So you say this is enabled right after the flashing and you did not actually ran "Encrypt phone" from this menu (that only works if battery charged above 80%)?
And when you boot into TWRP it asks for a password?

conmu said:
SYSTEM & DEVICE > Additional settings > Privacy: Advanced # Encrypt phone
If this it then that is point #2 from my initial message and that never finishes with any ROM I tried
So you say this is enabled right after the flashing and you did not actually ran "Encrypt phone" from this menu (that only works if battery charged above 80%)?
And when you boot into TWRP it asks for a password?
Click to expand...
Click to collapse
Never had to manually encrypt no.
Just choose a ROM with FBE enabled. That includes MIUI stock.
Flash it and then format data with TWRP.
On first boot it creates the encryption.
Then when you set a password this is your key.
When you boot to TWRP it will ask for the password to decrypt. Password is your pin.

Dobsgw said:
Never had to manually encrypt no.
Just choose a ROM with FBE enabled. That includes MIUI stock.
Flash it and then format data with TWRP.
On first boot it creates the encryption.
Then when you set a password this is your key.
When you boot to TWRP it will ask for the password to decrypt. Password is your pin.
Click to expand...
Click to collapse
Did you flash it via TWRP and formatted without reboot in the same session within TWRP? That is probably the only way I did not try.

conmu said:
Did you flash it via TWRP and formatted without reboot in the same session within TWRP? That is probably the only way I did not try.
Click to expand...
Click to collapse
Yeah that would be the best way.
Formatting data deletes entire SD card so back it up to PC!

Disabling system encryption on 8.1.0?

I was wondering if there existed a 'no-force encrypt' kernel I could flash to the Pixel C on 8.1.0?

Format data and then install magisk.

Monazite said:
Format data and then install magisk.
Click to expand...
Click to collapse
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?

fgaine said:
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?
Click to expand...
Click to collapse
Have you checked encrypted status in settings? Magisked boot.img should have disabled encryption if data partition is not encrypted. Or you need flash another kernel?
Sent from my Google Pixel 2 using XDA Labs

fgaine said:
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...yflasher-make-install-custom-kernels-t3537487
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Install as last step - after Magisk installation .. but normally Magisk is removing force-encryption too.
Are you sure you did format /data ?
Just wiping is not enough !
As it's not a development topic this thread should be moved to QA section ..
Anyway .. Good luck !

followmsi said:
https://forum.xda-developers.com/pi...yflasher-make-install-custom-kernels-t3537487
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Install as last step - after Magisk installation .. but normally Magisk is removing force-encryption too.
Are you sure you did format /data ?
Just wiping is not enough !
As it's not a development topic this thread should be moved to QA section ..
Anyway .. Good luck !
Click to expand...
Click to collapse
Thanks for the info. I'll try that later on. Don't fancy formatting and having to reinstall everything again for now. Cheers.

Question [URGENT] CAN'T INSTALL GSI

well, i've follow every single tutorial on a32 4g's xda page, even tried some youtube ones, but my phone just WON'T boot GSIs
it is not an a325F like most people, it's an a325M (the difference is that a325M support more LTE frequencies),
Well, i install samsung stock firmware, then install TWRP, run multidisabler, then format data, then reboot again, then factory reset and then finally installing the GSI as an .img file applied to System Image
that was the first method i tested, i tested many others, with no sucess
what happens, you may ask? the phone starts, show samsung logo with the classic warning above it, and after 3 secs it restarts.... a literal bootloop
can you guys help me? im tired of samsung's stock ONE UI, it's sooooo laggy

i've tried CrDroid, RiceDroid, Lineage with no success

i will try using DSU, ill return here later

installed the GSI using DSU sideloader w/ magisk, lets see if it boots

HEH didn't boot..... wtf is wrong with this phone???

i even tested GOOGLE'S OFICIAL GSI and it DIDNT BOOT.... yeah this phone is ****ted

applesucksLmao said:
i even tested GOOGLE'S OFICIAL GSI and it DIDNT BOOT.... yeah this phone is ****ted
Click to expand...
Click to collapse
Did you format your phone at each time? And do you have installed a thing in top of magisk? Try this magisk ---> https://huskydg.github.io/magisk-files/

kilam9900 said:
Did you format your phone at each time? And do you have installed a thing in top of magisk? Try this magisk ---> https://huskydg.github.io/magisk-files/
Click to expand...
Click to collapse
will try

doesn't work, even with no magisk it just bootloops

you know what, **** it, i had enough with this phone, guess ill just install normal ONE Ui and debloat it... the phone literally doesn't accept any GSI and bootloops, not even using android's own DSU system

Factory reset doesn't mean system wipe, it just means a data wipe. It goes back to Samsung's boot animation because OneUI is still installed.
Wipe Dalvik/ART Cache, System, Data and Cache and try again.
Have you also checked what kind of GSI your phone supports? Maybe it's A-Only, maybe it's AB.

Myrmeko said:
Factory reset doesn't mean system wipe, it just means a data wipe. It goes back to Samsung's boot animation because OneUI is still installed.
Wipe Dalvik/ART Cache, System, Data and Cache and try again.
Have you also checked what kind of GSI your phone supports? Maybe it's A-Only, maybe it's AB.
Click to expand...
Click to collapse
i did that yesterday, and it's virtual AB

Did you disable AVB/VBmeta?
applesucksLmao said:
you know what, **** it, i had enough with this phone, guess ill just install normal ONE Ui and debloat it... the phone literally doesn't accept any GSI and bootloops, not even using android's own DSU sys
Click to expand...
Click to collapse

kilam9900 said:
Did you disable AVB/VBmeta?
Click to expand...
Click to collapse
yep

applesucksLmao said:
yep
Click to expand...
Click to collapse
sure at 100%? because it could be this and even google says it

kilam9900 said:
sure at 100%? because it could be this and even google says it
Click to expand...
Click to collapse
ye i've done it

applesucksLmao said:
ye i've done it
Click to expand...
Click to collapse
Did you disable encryption?

kilam9900 said:
Did you disable encryption?
Click to expand...
Click to collapse
yes, with multidisabler and i even tried one time using a force decrypt zip

applesucksLmao said:
yes, with multidisabler and i even tried one time using a force decrypt zip
Click to expand...
Click to collapse
with anykernel one?

kilam9900 said:
with anykernel one?
Click to expand...
Click to collapse
what do you mean? i didn't flash any kernel, oh actually, i tried one time with the kernel someone posted here on a different thread