Hi everyone,
I would like to know if I can use device encryption in Lineage OS 15.1.
I currently have TWRP 3.2.2-0 installed on my Samsung Galaxy S5 Plus (kccat6).
Can TWRP 3.2.2-0 decrypt Lineage OS ?
By the past, I have seen many posts on forum, telling that they had trouble with the encryption or when they wanted to update LineageOS (which is currently in Nightly phase... so where updates can be important).
Thank you in advance for your answers !
Yes you can, but you have to update your TWRP to the latest version (3.2.3-0), they fixed the automatic installing of OTA zips on encrypted devices
Thanks lucaslbbh. So I made it. I was astonished to see that the process lasted only 9 min... Unfortunately, my phone was unable to start after that (bootloop).
I came back to TWRP, entered my password and restored my Nandroid backup.
Surprinsgly, it kept the encryption : I have to enter my PIN for each startup, and when I want to enter in TWRP. In the security menu, it's said it's encrypted.
Is it possible ?
oldbear3 said:
Thanks lucaslbbh. So I made it. I was astonished to see that the process lasted only 9 min... Unfortunately, my phone was unable to start after that (bootloop).
I came back to TWRP, entered my password and restored my Nandroid backup.
Surprinsgly, it kept the encryption : I have to enter my PIN for each startup, and when I want to enter in TWRP. In the security menu, it's said it's encrypted.
Is it possible ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
This guide was only tested with Nougat but it says the ROM has to be unrooted when encrypting /data. Maybe that's your prob?
Related
Hello, after i got my op3 i instant decrypted it with fastboot and installed freedomos because i heard there could be problems with rooting etc.
But now i heard, that you can use Customroms and twrp even with encrypted storage, what i find really nice so thiefes can't access my data easily.
Now the question is, can i simply encrypt my device in settings -> security with a password and can i simply enter the password in twrp then, and is the behavior the same as the forced encryption on stock oxy?
Also i have another problem, i cant use cm13, cm14 and resurrectionremix, because it stucks on the op logo on boot. I read that this because the data is decrypted. Will encryption fix this problem or do i have to do the method2 of the unbrick guide to fix it? Well, i can just use my nandroid restored freedomOS rom at the moment, any other roms results in a bootfreeze, even if i update freedomos.
Best regards and thanks for your help guys :fingers-crossed:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.
Hi everybody,
After the cm13 on my Zenfone 2 (ZE551ML / Z200A) crashed down with no recent backups, I decided to upgrade to Lineage OS 14 now that I had to reinstall the ROM anyways. And now I'm stuck:
My device is encrypted (as it always has been). Since the first boot of Lineage OS the encryption method seems to have changed to an Android Nougat - specific encryption method. That means:
My installed TWRP 3.0.2 is now unable to decrypt the phone (known issue, as I found out).
The TWRP version 3.1 that would be able to decrypt it, is however not available for my Zenfone 2.
Even without a screen password, PIN or pattern set, TWRP still promts for a decryption password.
Without the TWRP working, I believe I cannot make any changes to the system, e.g. downgrading back to cm13, without wiping the entire internal storage.
The only thing that does seem to work is ADB sideload, but even so, Google Play Services installed from a side-loaded GAPPS e.g. doesn't work.
Now, how can I restore a state on that phone model where I have a working TWRP recovery that can modify the system partition?
Is there maybe an unofficial TWRP 3.1 for the Zenfone 2 or an alternative recovery that does handle the Nougat encryption?
Or is it somehow possible to downgrade back to cm13 without decrypting yet without losing all data on the internal storage?
I'm scared of trying to compile TWRP 3.1 from the source code myself as I have no experience "building" whatsoever.
Thanks for your help!!
Have you tried 3.0.3 available in the LinOS thread?
Sent from my ASUS_Z00A using Tapatalk
Yes, as available on theflamingskull.com. Either version cannot decrypt the phone (even when re-installed).
This one works for my encrypted phone (encrypted with CM14.1):
https://www.androidfilehost.com/?fid=457095661767154983
Even with encrypted f2fs (changed to f2fs with this one).
Z200A is Z00A Essentially, right?
If yes: https://infinitus-rom.com/devices/asus/asus-z00a
You can download TWRP 3.1.0 there
I use this one too, it works flawlessly
Thank you!! Those worked! For some reason I always flashed version 3.0.3-M3 without noticing the M3 at the end. Starting with version 3.0.3-M4 as you linked, I was able to get back into recovery decrypting my phone! :good:
Hi there,
My overall goal is to flash lineage os on my nexus 5x. For that I downloaded TWRP and flashed it on my nexus 5x according to this description:
https://www.techrrival.com/twrp-recovery-root-nexus-5x/
Everything worked fine until here and when now I go into TWRP it asks me for the decryption password and I entered the one which I used for the lock screen, but for some reasons it didn't accept it. So I tried all the passwords I normally use but none of them seem to match the decryption password. Since nothing seem to word I flashed the factory Image (+wiped everything) according to:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
in the hope that this would reset my encryption password when I enter a new password when setting the device up. I then again flashed TWRP and tried to enter but the encryption password is still wrong.
Because of this stupid encryption I don’t have access to the user data where I put the image of the Lineage OS build when using TWRP. So please can somebody help me? Thank you.
xXApiXx said:
Hi there,
My overall goal is to flash lineage os on my nexus 5x. For that I downloaded TWRP and flashed it on my nexus 5x according to this description:
https://www.techrrival.com/twrp-recovery-root-nexus-5x/
Everything worked fine until here and when now I go into TWRP it asks me for the decryption password and I entered the one which I used for the lock screen, but for some reasons it didn't accept it. So I tried all the passwords I normally use but none of them seem to match the decryption password. Since nothing seem to word I flashed the factory Image (+wiped everything) according to:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
in the hope that this would reset my encryption password when I enter a new password when setting the device up. I then again flashed TWRP and tried to enter but the encryption password is still wrong.
Because of this stupid encryption I don’t have access to the user data where I put the image of the Lineage OS build when using TWRP. So please can somebody help me? Thank you.
Click to expand...
Click to collapse
I guess you don't have the lastest TWRP.
Get at least 3.2.1
Official download page : https://eu.dl.twrp.me/bullhead/
Thank you for responding. I have always used the version which you sugested and today I flashed the TWRP from your link but still encryption password is wrong. :'( I dont know what else I could try.
Just now I flashed the factory image of android 6.0 and then TWRP but again encryption passoword is incorrect. I am really frustrated...
Why is this so hard to flash a custom rom on the nexus device. It was so easy on my dad's Xioami Redmi Note 4x.
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Ms0206 said:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Click to expand...
Click to collapse
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
kurtn said:
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
Click to expand...
Click to collapse
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Ms0206 said:
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Click to expand...
Click to collapse
Your data Partition is encrypted. Sideload does not touch data partition. Follow the guide
As if I didn't know it before, following the official guides producing the same errors as using Twrp.
I tried so many things...using official recovery does not install OTA automatically.
Sideload producing the same errors as using Twrp - "Magisk addond.d failed, cannot find Magisk binaries, reflash OTA Form decrypted recovery or reflash Magisk".