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.
Related
Hi, thanks for all the information here.
Thanks to the guides, I was able to downgrade, backup TA, upgrade, build personal kernel, install twrp, working android pay.... everything is good. But:
I have tested out some modules for Magisk, two I wanted to use boot me in a boot loop/stuck on boot.
I can fix this using TWRP, I just use mount_magisk stored in my download on internal storage.
Then I disable the 'bad' module, by typing in the terminal: /magisk/<module folder>/disable
BUT!
This only works because my data is decrypted.
I want to encrypt my data.
It is true we still don't have a TWRP that supports our encryption?
If I encrypt, is there anyway to disable a bad magisk module?
I think magisk is stored in the boot, correct? So it is not in data, so it does not matter if data is encrypted or not?
I hope someone can clear up some of my worries.
Thanks
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
Ok, so if I wanted to recover my system, I could just reflash boot (my kernel)?
I would have to install magisk again but that is ok.
But would I even be able to install magisk if my data is encrypted?
I think v12 can be installed if no access to /data, but v13 not?
Thanks
ypnos42 said:
While Magisk itself is part of the boot image, its configuration and modules are located in /data/magisk. mount_magisk does not work without a decrypted data partition.
Click to expand...
Click to collapse
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
I don't have an encrypted partition. Could anybody with encrypted partition try it?
voilsb said:
According to this thread (https://forum.xda-developers.com/x-compact/development/advanced-stock-kernel-twrp-xperia-x-t3464685), TWRP 3.0.2 supports decryption. I haven't tested it personally, but that's the version I used.
Click to expand...
Click to collapse
Yes it does say that, but it is talking about fw version 34.1.A.1.198 - which is marshmallow right?
From what I understand TWRP was fine with XC's encryption in marshmallow, but with nougat it doesn't work.
So I think (that version of) TWRP will not work. (but I have not tested myself, but I read a post somewhere saying it didn't)
I need to decrypt the data to get an app working, since it needs to change the data partition to do so. Is there any way to decrypt the data? Thanks!
Elecrolo said:
I need to decrypt the data to get an app working, since it needs to change the data partition to do so. Is there any way to decrypt the data? Thanks!
Click to expand...
Click to collapse
If you unlock the bootloader, flash twrp and then use twrp to flash the dm no verity zip, then format your data (this all wipes your data from the phone of course so you'll need to setup again) you will be unencrypted. You will also likely need a custom recovery to change the /data partition to a different format other than f2fs.
i encrypted my phone after i root it. It's running Lineageos. Encryption works, but if i boot in recovery i can enter folders but don't see any data. I can not mount data folder or add/install anything. Looks logic because it's encrypted, but i read somewhere that twrp will ask for a password when system is encrypted. I don't get this message.
Any suggestion how i need to do it correct? that i can enter twrp with pass
whitetornado said:
i encrypted my phone after i root it. It's running Lineageos. Encryption works, but if i boot in recovery i can enter folders but don't see any data. I can not mount data folder or add/install anything. Looks logic because it's encrypted, but i read somewhere that twrp will ask for a password when system is encrypted. I don't get this message.
Any suggestion how i need to do it correct? that i can enter twrp with pass
Click to expand...
Click to collapse
AFAIK you need a recovery that supports encryption.
strongst said:
AFAIK you need a recovery that supports encryption.
Click to expand...
Click to collapse
i have twrp 3.2.1-0, question, how to start the ask password in terminal or recovery mode, if it is possible?
The only recovery i know which does support encryption is the 32 Bit shreps recovery. Do keep in mind that if you encrypt your device and use that recovery you won't be able to flash 64 bit roms since no 64 bit recovery supports encryption
I'm sorry if this is posted again but I can't find anything about my problem.
My Mi A1 in unrooted.
I had installed gcam without rooting it to continue receiving OTA, after the latest update I wanted to disable gcam. During the process the application unlocked the bootloader but didnt lock it again.
When I disabled it after the reboot my phone did a factory reset and enrypted itself. I want to decrypt my phone so I used some ways I found on the internet like:
Simple factory reset.
Locked bootloader.
Factory reset again, even though after the lock it did it itself.
Flashed fastboot stock rom.
Flashed twrp read only, wiped system and flashed fastoboot stock rom again!
Still the phone forced encrypt itself after every way I tried:
For gcam I used this way: https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
I didn't check the thread because I already had the app to do the installation.
For fastboot installation I used this: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
EDIT: What if I unlock the bootloader with MiUnlock and relock it via fastboot?
Phone is encrypted by default. Why would you want to have it decrypted? But if you insist.. you have to install magisk, disable forced encryption and reformat data partition in TWRP.
Locking or unlocking the bootloader after May update wipes your data, this is normal for Android and now our phones.
Encryption is default, it would have been encrypted before the wipe as it is now after the wipe, why do you want it unencrypted?
kudos1uk said:
Locking or unlocking the bootloader after May update wipes your data, this is normal for Android and now our phones.
Encryption is default, it would have been encrypted before the wipe as it is now after the wipe, why do you want it unencrypted?
Click to expand...
Click to collapse
Thank you very much, I never experienced this again after unlocking so I thought it was because of the encrypt, I hadn't checked if it was encrypted before the wipe and I assumed it wasn't.
_mysiak_ said:
Phone is encrypted by default. Why would you want to have it decrypted? But if you insist.. you have to install magisk, disable forced encryption and reformat data partition in TWRP.
Click to expand...
Click to collapse
I didn't know the phone was encrypted by default.
Thank you for the possible way though.
Yeah, it is encrypted by default and hw encryption is used. So don't think that it can affect your performance in any way.
_mysiak_ said:
Phone is encrypted by default. Why would you want to have it decrypted? But if you insist.. you have to install magisk, disable forced encryption and reformat data partition in TWRP.
Click to expand...
Click to collapse
After reformatting data partition, do I need to do anything else?
ubmit said:
After reformatting data partition, do I need to do anything else?
Click to expand...
Click to collapse
Keep Magisk installed, otherwise it will probably get encrypted again by stock boot image. Not sure, I didn't try it.. I want my data secure.
I have unlocked the boot-loader and also installed TWRP recovery on my X00_TD device which has 'Pie' as it's Stock ROM.
Now, I would like to know how to proceed to do rooting on this device.
Is it necessary to run decrypt zip file before we run 'magisk-v19.1' to root?
Please advise!
Decrypt removes another variable from the process, so yeah it might be good to remove a probable failure point.
Decrypt and then Magisk?
arko9699 said:
Decrypt removes another variable from the process, so yeah it might be good to remove a probable failure point.
Click to expand...
Click to collapse
So , irrespective of the state of the device one needs to flash the decrypt file first and then flash the magisk to root the device, right?
Please advise!
Kudla said:
So , irrespective of the state of the device one needs to flash the decrypt file first and then flash the magisk to root the device, right?
Please advise!
Click to expand...
Click to collapse
When rooting mine I used the decrypt.zip . When you factory reset the phone will take some time to encrypt your data and this prevents that. It will hinder you from flashing stuff from the internal storage in TWRP. You can use magisk without it too.
Unable to Mount Storage?
arko9699 said:
When rooting mine I used the decrypt.zip . When you factory reset the phone will take some time to encrypt your data and this prevents that. It will hinder you from flashing stuff from the internal storage in TWRP. You can use magisk without it too.
Click to expand...
Click to collapse
I went ahead and flashed magisk without flashing decrypt. The root was successful!
Now, when tried to clear cache via TWRP it says 'Unable to Mount Storage'. What could be the reason here?
Is it safe to wipe dalvik/art cache?
Please advise!
Kudla said:
I went ahead and flashed magisk without flashing decrypt. The root was successful!
Now, when tried to clear cache via TWRP it says 'Unable to Mount Storage'. What could be the reason here?
Is it safe to wipe dalvik/art cache?
Please advise!
Click to expand...
Click to collapse
Try to run decrypt.zip it should fix the problem. I used a OTG device since I didn't have a SD card. Unless you run decrypt.zip you cannot use the internal storage. So I would recommend running it despite my last statement.