Database Develop

Went to bed with an encrypted phone.

And this morning the phone was acting weird. I rebooted the phone and did not get the screen to unlock before the phone boots. Now I see the phone is no longer encrypted. Anybody else have this happen?
I'm stock with with faux kernal.

Larzzzz82 said:
And this morning the phone was acting weird. I rebooted the phone and did not get the screen to unlock before the phone boots. Now I see the phone is no longer encrypted. Anybody else have this happen?
I'm stock with with faux kernal.
Click to expand...
Click to collapse
mines encrypted, and mine doesn't have an unlock code, as i didnt set one up. how do you know your device in unencrypted? or are you just assuming it is? you have to format your data before ypu can decrypt it btw. if you gobinto your main settings, security, itll tell you if your phone is encrypted or decrypted.

I looked in the settings/security and saw this... If I'm reading this correctly, the phone is no longer encrypted.

Larzzzz82 said:
I looked in the settings/security and saw this... If I'm reading this correctly, the phone is no longer encrypted.
Click to expand...
Click to collapse
yup, looks like its decrypted. as heres my encryoted n6..

and how does a phone decrypt itself?

Larzzzz82 said:
and how does a phone decrypt itself?
Click to expand...
Click to collapse
good question! maybe a derp somewhere.. have you rebooted since?

I did reboot because chrome and messaging would not open up. The icon would get a white halo around them yet nothing would happen. Upon rebooting I was not asked for my pattern lock before Android fully booted

Larzzzz82 said:
I did reboot because chrome and messaging would not open up. The icon would get a white halo around them yet nothing would happen. Upon rebooting I was not asked for my pattern lock before Android fully booted
Click to expand...
Click to collapse
did u factory reset the phone from recovery?

Nikos2k said:
did u factory reset the phone from recovery?
Click to expand...
Click to collapse
Through twrp, yes, last night. Just what was recommended. I did not do anything in the advanced settings

Larzzzz82 said:
Through twrp, yes, last night. Just what was recommended. I did not do anything in the advanced settings
Click to expand...
Click to collapse
The reset probably disabled the encryption
Re-encrypt it through Security settings

Nikos2k said:
The reset probably disabled the encryption
Re-encrypt it through Security settings
Click to expand...
Click to collapse
The phone was decrypted before I reset. It was never decrypted to begin with until yesterday when I was having issues with a couple of apps. I rebooted and I decided to check if it was because it didn't ask for my pattern lock as it used to when booting up.

Larzzzz82 said:
The phone was decrypted before I reset. It was never decrypted to begin with until yesterday when I was having issues with a couple of apps. I rebooted and I decided to check if it was because it didn't ask for my pattern lock as it used to when booting up.
Click to expand...
Click to collapse
As far as I know, there is no way to decrypt the contents of an encrypted nexus6 (which is not the same as disabling encryption, as an actual decryption of the device would preserve the contents of the device)
Since you now have an unencrypted device, the contents of your device must have been erased during the disabling of the encryption

Nikos2k said:
Since you now have an unencrypted device, the contents of your device must have been erased during the disabling of the encryption
Click to expand...
Click to collapse
No, they weren't. Everything was intact.

Larzzzz82 said:
No, they weren't. Everything was intact.
Click to expand...
Click to collapse
I don't think that android5 has a function to decrypt the whole content of the device.
In this page about how encryption works its says "New Android 5.0 devices encrypted at first boot cannot be returned to an unencrypted state."
And obviously it should be so.
Anyway, maybe it's better that you factory reset the device and encrypt it afterwards so that you set a pin yourserf
(android5 devices are encrypted on first boot, and there is no password)
When you had the pattern security option set, did TWRP ask for any password?
And if yes, how did you input the pattern?

TWRP does not ask me for a password. I broke the seal on the box of this phone came in. It was set up before I had a sim card in it.the phone was encrypted. I did look within the first week or two of my owning it. aside from unlocking, rooting, and a couple of mods, it is stock. I am NOT using a custom ROM. I have installed faux kernel within the last couple of weeks and the request for a pattern unlock in the middle of booting Android remained until the other day. To say I am perplexed as an understatement.

Larzzzz82 said:
And this morning the phone was acting weird. I rebooted the phone and did not get the screen to unlock before the phone boots. Now I see the phone is no longer encrypted. Anybody else have this happen?
I'm stock with with faux kernal.
Click to expand...
Click to collapse
When did you install the kernel and had you done a TWRP factory wipe prior to the install?
Your post made me double check my phone - I am now unencrypted
Earlier this week I had had done a TWRP (2.8.4.0) factory wipe to do a clean install of CleanROM 1.4 and I think TWRP did a full decrypt wipe without me wanting to do so when it was supposed to do a simple reset

SP_Kenny said:
When did you install the kernel and had you done a TWRP factory wipe prior to the install?
Your post made me double check my phone - I am now unencrypted
Earlier this week I had had done a TWRP (2.8.4.0) factory wipe to do a clean install of CleanROM 1.4 and I think TWRP did a full decrypt wipe without me wanting to do so when it was supposed to do a simple reset
Click to expand...
Click to collapse
The factory wipe in TWRP, besides wiping everything, it disabled the forced encryption, so you have to select encrypt yourself if you want it to be encrypted.
And "CleanROM is decrypted by default. This means if you are encrypted or are decrypted you will stay that way! It wont change you crypto settings!"
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
Larzzzz82 said:
TWRP does not ask me for a password. I broke the seal on the box of this phone came in. It was set up before I had a sim card in it.the phone was encrypted. I did look within the first week or two of my owning it. aside from unlocking, rooting, and a couple of mods, it is stock. I am NOT using a custom ROM. I have installed faux kernel within the last couple of weeks and the request for a pattern unlock in the middle of booting Android remained until the other day. To say I am perplexed as an understatement.
Click to expand...
Click to collapse
Anyway, you can encrypt it yourself, but if you select a pattern instead of pin/password in the security settings, i do not think that you will be able to access the data in TWRP as it seems there is no way to input the pattern in TWRP
So b4 entering recovery, u will have to change the security setting

In the past when I had done a factory rest / wipe via TWRP it had not changed my encryption. This only happened with the current version and gave no indication that it was going to be in an unencrypted state
Sent from my Nexus 6 using XDA Free mobile app

I like my security so I guess I'll just leave my device encrypted. I believe if I decrypted, it wouldn't really make it that much faster than this?

Apologies if this was suggested further in the thread, and that I'm replying to an old post. But I recently had this problem and figured out a solution.
- Accessibility was enabled and for some reason this cached the boot password. So- when I removed the app (rights) and turned off accessibility, and changed (reset/reentered) the password in security settings... On next boot the phone correctly asked me for password.

Are ROM's not Encryption Enabled?

I'm new to the 6 and I haven't really read too much into the whole encryption thing, so I don't know the pros/cons of having it that way, or not.
During my first boot of this thing, I started the unlock/root process, then I quickly remembered about encryption...and what the whole thing was about. Well I'm curious, are these custom ROM's built without the encryption? In the security menu of Chroma, encryption is enabled. In another ROM which specifically stated encryption was off...it was actually on.
So I'm confused.
Thanks.

Some ROMs do not force encryption. They can still be encrypted. It depends on the kernel. You will need to perform a wipe to unencrypt

stevew84 said:
I'm new to the 6 and I haven't really read too much into the whole encryption thing, so I don't know the pros/cons of having it that way, or not.
During my first boot of this thing, I started the unlock/root process, then I quickly remembered about encryption...and what the whole thing was about. Well I'm curious, are these custom ROM's built without the encryption? In the security menu of Chroma, encryption is enabled. In another ROM which specifically stated encryption was off...it was actually on.
So I'm confused.
Thanks.
Click to expand...
Click to collapse
It depends on the state of your device before you flash the ROM. If you are unencrypted prior to flashing the ROM, you will stay unencrypted. And if encrypted, you will stay encrypted. For most ROMs. Read the fine print in the OP.

cam30era said:
It depends on the state of your device before you flash the ROM. If you are unencrypted prior to flashing the ROM, you will stay unencrypted. And if encrypted, you will stay encrypted. For most ROMs. Read the fine print in the OP.
Click to expand...
Click to collapse
I've also read about long "encrypting now" screens during first boot of fresh ROM's, I've never seen those.

Encryption depends on the kernel or more accurately the fstab, so it depends what kernel is supplied with the ROM or which kernel you plan on flashing with the ROM.
There are 2 types of ROM. Stock based and AOSP based. I find it hard to believe any AOSP ROM dev would turn on force encryption, but with a stock ROM, it could be on or off - depending. Read each thread to find out.
All ROMs and kernels are encryption enabled by the way. Turning off force encryption inky prevents first boot from encrypting your data partition. You can still turn on encryption yourself in settings and if you're already encrypted, turning off force encryption will not unencrypt your data, so it will still be on. Once force encryption has been turned off, you must then format /userdata to remove encryption

stevew84 said:
I've also read about long "encrypting now" screens during first boot of fresh ROM's, I've never seen those.
Click to expand...
Click to collapse
Correct. If you are unsure of your kernel status go to Settings/Security/Encryption. If it says "Encrypt phone", then you are unencrypted.

cam30era said:
Correct. If you are unsure of your kernel status go to Settings/Security/Encryption. If it says "Encrypt phone", then you are unencrypted.
Click to expand...
Click to collapse
Ah alright, well each and every time I flash something new, I'm encrypted. I'm interested in getting rid of that, but not sure exactly how to do it.

stevew84 said:
Ah alright, well each and every time I flash something new, I'm encrypted. I'm interested in getting rid of that, but not sure exactly how to do it.
Click to expand...
Click to collapse
It says in my post

Encryption will stay on unless you completely wipe the device and have a kernel installed that doesn't force you to encrypt. So you'll never see an option for decrypting your device. This comes with a huge warning that ANYTHING on the internal storage will be lost, that goes for the ROM and your files, including your ROM zip files for flashing. If you want to decrypt the device I suggest you first practice by flashing a ROM that you copy into your phone while in recovery so you know you can do it.
Guide: http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
This will get you to a clean slate, make sure you test MTP (file transfer over usb from computer) in recovery and verify that you can move files over to your device in recovery. You should already have a custom recovery installed such as TWRP. If you are considering disabling make sure you know exactly what is going on first, its not as straight forward as it seems. Goodluck

stevew84 said:
Ah alright, well each and every time I flash something new, I'm encrypted. I'm interested in getting rid of that, but not sure exactly how to do it.
Click to expand...
Click to collapse
If you are on stock, rooted, or a non-CM12 based ROM, one way is to go here > http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Remember, after flashing the boot.img, you need to "fastboot format userdata" to unencrypt. This will wipe your SDcard.

rootSU said:
It says in my post
Click to expand...
Click to collapse
Sorry, I didn't see you posted.
Right now with Chroma + Vindicator kernel...Encryption states Enabled in the security menu.

stevew84 said:
Sorry, I didn't see you posted.
Right now with Chroma + Vindicator kernel...Encryption states Enabled in the security menu.
Click to expand...
Click to collapse
Because you were already encrypted.

stevew84 said:
I don't know the pros/cons of having it that way, or not.
Click to expand...
Click to collapse
Pros for encryption;
- security. This is pretty obvious, if somebody hostile gets their hands on your phone, your data will not be obtained by them.
Cons;
- performance and battery life. There is indication in AOSP that google *intends* to activate hardware crypto, but as of yet, have not. That means that the crypto function is done on your main CPU, which is (a) not as fast as the hwcrypto block, and (b) takes up valuable CPU cycles from other software that is running, and (c) anything that uses CPU heavily will consume battery.

Another con with encryption that I have (which I admit is extremely unlikely - but has happened in the past) is that files that are backed up off the device may not get decrypted correctly, leaving them corrupt. That is my main hate of encryption. That and the fact that I cannot automate my TWRP backups

rootSU said:
Another con with encryption that I have (which I admit is extremely unlikely - but has happened in the past) is that files that are backed up off the device may not get decrypted correctly, leaving them corrupt. That is my main hate of encryption. That and the fact that I cannot automate my TWRP backups
Click to expand...
Click to collapse
That isn't a con of encryption. That's a con of using broken software to perform your backup.

doitright said:
That isn't a con of encryption. That's a con of using broken software to perform your backup.
Click to expand...
Click to collapse
The con of encrypting data is that it may not always decrypt-able. Regardless of the root cause being Android, Windows, Linux or "broken software". If doing something to your data leads to it being useless via whatever means, then there is a negative effect of doing that something to your data

CM Encryption

I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.

BEDickey said:
I was wondering if how to go about encrypting our phones on CM 12.1. For me all it does is restart the phone and boot to lock screen.
Click to expand...
Click to collapse
Settings --> Security - First thing listed should be encrypt phone.

I know that. I'm saying all that does is restart it to the lock screen, as I said. The phone is not actually encrypted in the process like it should, it just restarts.

With Mofo root, you had to encrypt on an unrooted stock ROM, then flash the rooted ROM after. Are similar also required with CM?

I'm not sure but you can temp disable root in CM by A) Disbaling it in SuperSU app - Uncheck "Enable Superuser" or B) In the settings under developer options - Change "root access" to "disabled". Try that and encrypt then re-enable after

Thanks! I will check it out and report back.

I'm having the exact same problem. I was never able to encrypt running total stock, computerfreek rom, or rremix rom. Device briefly shows the green android, then begins a soft reboot and then a full reboot. I have tried disabling root (both ways) as suggested above. It makes no difference.

Same here, I have the same situation. It seems as though either CM itself or the act of unlocking to bootloader has removed the ability to encrypt your phone. Any advice from people more in the know would be helpful.

In my case, I have never been able to encrypt... even with a totally stock, unmodified, unrooted, unmofo'd, bootloader locked device. Googling around, it seems like a problem where the disk is partitioned in such a way that there isn't the required space left for encryption to initiate. Anything looking like a solution was way over my comfort level (manual repartitioning via terminal), or in the case of some flashable scripts, was outdated.

Question: Did either of you change the format of your /data partition in TWRP to maybe ExFAT or F2FS?

I have never formatted anything.

I think it's one of things you cannot do, since the bootloader is unlocked. IIRC, it must be locked, regardless of the manufacturer. That's why we have the bootloader toggle in dev options.
Sent from my DROID Turbo using Tapatalk

Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.

P_6 said:
Any updates on this... I have to believe there is some way to encrypt these devices, even if rooted with a custom rom. Rooting and installing a ROM in and of themselves do not diminish the added security provided by full device encryption.
Click to expand...
Click to collapse
This worked for me:
1. Flash back to 100% stock.
2. Encrypt through security settings.
3. Flash whatever you want afterwards. The encryption will be preserved.
I'm currently encrypted and running CF's rom with no issues. A bootloader unlock does not prevent encryption from working.

Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)

P_6 said:
Thanks for your response to this... I'm at Step 3, and using TWRP (Tried both 2.8 and 3.0) to flash CF 1.2.8. However, it will not successfully decrypt, regardless of what password I provide it (have tried complex & simple passwords, and the defaults listed out there, etc)
Click to expand...
Click to collapse
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.

TheSt33v said:
That's weird. The password should be the same as your lockscreen password. If you used a pattern lock, each dot on the pattern corresponds to a number, although I'm not sure which dot is which number. If your lockscreen password doesn't work, something went wrong and you'll probably have to wipe your phone to fix it.
Click to expand...
Click to collapse
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?

P_6 said:
That's what I figured. From what I've been reading, it should work just fine. I used an alphanumeric password to secure the phone, could that be part of the issue?
Click to expand...
Click to collapse
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.

TheSt33v said:
I doubt it. I used Cerberus to remotely change my pin to an alphanumeric password and then I forgot about it. When I rebooted the phone, I had to enter that password to decrypt the phone. It worked fine.
Click to expand...
Click to collapse
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.

P_6 said:
So, using a simple 4 digit pin, I got TWRP to decrypt data. I installed CF 1.2.8 and changed my password to something more secure. I rebooted and got stuck in a bootloop. I've tried just about everything since, multiple wipes, reinstalls via TWRP, no dice. The encryption is still intact, but I can't get CF to boot.
Click to expand...
Click to collapse
Weird. You might have to start all over again by going back to stock, and this time either keep the pin or just not deal with encryption.

Broken Fire launcher fix

I tried to remove amazon fire launcher with the first two commands on this thread "http://forum.xda-developers.com/amazon-fire/development/tut-remove-default-launcher-amazon-fire-t3288310" but now its buged out and i can't fix it. I can root if needed but is there a easy fix. I did try a ota update but that did not work. Also i would like to keep my data.
Reuben

Reuben Talbott said:
I tried to remove amazon fire launcher with the first two commands on this thread "http://forum.xda-developers.com/amazon-fire/development/tut-remove-default-launcher-amazon-fire-t3288310" but now its buged out and i can't fix it. I can root if needed but is there a easy fix. I did try a ota update but that did not work. Also i would like to keep my data.
Click to expand...
Click to collapse
Reload FireOS 5.3.1 (or 5.3.2 if you don't immediately care about root) from the stock recovery menu. Your apps and data will remain intact.

I tried that 5 times two days ago But it does nothing

Davey126 said:
Reload FireOS 5.3.1 (or 5.3.2 if you don't immediately care about root) from the stock recovery menu. Your apps and data will remain intact.
Click to expand...
Click to collapse
Reuben Talbott said:
I tried that 5 times two days ago But it does nothing
Click to expand...
Click to collapse
Well, once would have been sufficient.
If the problem persists:
- FireOS reloads are not occurring successfully (assume you have ruled that out)
- may have to bite the bullet and wipe the user data partition prior to reloading FireOS
- defective device (seems highly unlikely...)
If still no joy you can root, install FlashFire and use the 'wipe' function to completely purge your device of all content. Then reload FireOS via the stock recovery menu which will yield a fresh-out-of-the-box experience. Recommend using the 'SuperTool' to root as it also installs SuperSU (and removes KingUser) which is a FlashFire prerequisite.

I don't think I have a defective device I have had it sense July and its worked well until I Dido those commands

Davey126 said:
Well, once would have been sufficient.
If the problem persists:
- FireOS reloads are not occurring successfully (assume you have ruled that out)
- may have to bite the bullet and wipe the user data partition prior to reloading FireOS
- defective device (seems highly unlikely...)
If still no joy you can root, install FlashFire and use the 'wipe' function to completely purge your device of all content. Then reload FireOS via the stock recovery menu which will yield a fresh-out-of-the-box experience. Recommend using the 'SuperTool' to root as it also installs SuperSU (and removes KingUser) which is a FlashFire prerequisite.
Click to expand...
Click to collapse
Do you think i could wipe only the system partition and keep my data?

Reuben Talbott said:
I don't think I have a defective device I have had it sense July and its worked well until I Dido those commands
Click to expand...
Click to collapse
Reuben Talbott said:
Do you think i could wipe only the system partition and keep my data?
Click to expand...
Click to collapse
Can't hurt to try. Be aware that once you wipe the system partition the device will no longer boot into FireOS. If necessary you will need to power down the device (long press power button) and then boot into stock recovery using <power>+<vol-up>. Also note that while well considered/executed wipes are generally safe there is always the chance something could go wrong leaving you with an unbootable brick. Rather rare but would be irresponsible not to point out possibility since you seem to have some valuable data on the device. Might want to copy that to the SD card in advance (if possible).

Davey126 said:
Can't hurt to try. Be aware that once you wipe the system partition the device will no longer boot into FireOS. If necessary you will need to power down the device (long press power button) and then boot into stock recovery using <power>+<vol-up>. Also note that while well considered/executed wipes are generally safe there is always the chance something could go wrong leaving you with an unbootable brick. Rather rare but would be irresponsible not to point out possibility since you seem to have some valuable data on the device. Might want to copy that to the SD card in advance (if possible).
Click to expand...
Click to collapse
That is what is what I was thinking of doing.

Does any one know were app data is stored?

Reuben Talbott said:
Does any one know were app data is stored?
Click to expand...
Click to collapse
Many places. There are guidelines but somedevelopers opt to ignore. You'll need to do some searching and hope that you find everything. Could also try Android's native app backup/restore commands which operate via adb (USB tether). Do some goggling for syntax.

LineageOS: Encrypted phone, all data gone

I thought that while encrypting my phone, the result would be that my data is preserved, just encrypted. So I went through the encryption process only to find that all my data is wiped, so that I have to restore everything from backups, as far as I have them.
Did I overlook something, or is this a bug? I have LineageOS 14.1, installed yesterday, official.

Found that after a reboot, the data was again gone. (after I spent considerable time setting the phone up yet again), now factory reset, running unencrypted, until I know what has been going wrong here. Sigh. Custom roms and encryption continue to be a toxic mix for me.

yahya69 said:
Found that after a reboot, the data was again gone. (after I spent considerable time setting the phone up yet again), now factory reset, running unencrypted, until I know what has been going wrong here. Sigh. Custom roms and encryption continue to be a toxic mix for me.
Click to expand...
Click to collapse
When I first started playing around with encryption (Samsung Note 3) I discovered that to get encryption to work properly I had to format /data (you lose everything, including internal shared storage) and that it worked better on stock ROM rather than custom ROMs.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
When I first started playing around with encryption (Samsung Note 3) I discovered that to get encryption to work properly I had to format /data (you lose everything, including internal shared storage) and that it worked better on stock ROM rather than custom ROMs.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
which I kind of accepted after learning it the hard way, but the problem was that after encrypting the device, all data was wiped each time the phone was rebooted, so something is buggy here.

yahya69 said:
which I kind of accepted after learning it the hard way, but the problem was that after encrypting the device, all data was wiped each time the phone was rebooted, so something is buggy here.
Click to expand...
Click to collapse
I resolve this problem using latest official twrp.

dimon2242 said:
I resolve this problem using latest official twrp.
Click to expand...
Click to collapse
How did you? (What version of TWRP did you install) After all, it is not TWRP that does the encryption, or is it? So I don't see how this could be the cause.
With TWRP, I had the additional issue that it kept asking me for a password to mount /data, but it wouldn't accept the PIN that I had set in Android. I have no idea what other password it might want.
Oh, well, there is just too much fumbling in the dark in this whole mobile devices business. I have been a Linux user for some 20 years, and there, if things go wrong, you can actually view what is happening. On android, this is so much more difficult, even with logcat.

yahya69 said:
How did you? (What version of TWRP did you install) After all, it is not TWRP that does the encryption, or is it? So I don't see how this could be the cause.
With TWRP, I had the additional issue that it kept asking me for a password to mount /data, but it wouldn't accept the PIN that I had set in Android. I have no idea what other password it might want.
Oh, well, there is just too much fumbling in the dark in this whole mobile devices business. I have been a Linux user for some 20 years, and there, if things go wrong, you can actually view what is happening. On android, this is so much more difficult, even with logcat.
Click to expand...
Click to collapse
Have you tried default_password as the password in TWRP?
Also, if you can actual log into your system normally, then you can set the password again and require it on boot.

BillGoss said:
Have you tried default_password as the password in TWRP?
Click to expand...
Click to collapse
What "default password"? You mean, literally typing "default_password"? No I did not. What would that have done?
After all, again, it required a password for the /data partition, hence a password with whom it is encrypted. But I had used no password other than the PIN. And again, I can't see how my problem of data disappearing on each boot would be caused by TWRP.
Also, if you can actual log into your system normally, then you can set the password again and require it on boot.
Click to expand...
Click to collapse
Again, what password do you have in mind? The PIN? Yes, the system asked for the PIN at boot, but nonetheless, all data was wiped on each boot.
For the time being,I run the system without encryption, because I have had enough of setting is up again and again anew (had to do this three or four times.)
Again, it looks like this is a bug. Because after initially encrypting the phone, my data should still have been there. But it was gone. The phone was now encrypted, but there was nothing on it. That's something that I am pretty sure is not supposed to happen.

just had the same using Samsung S5 Duos with latest lineage-os (20180427): this is a cluster-f**k, I cannot believe it. I advocate using Lineage-OS whereever I go. Of course, it's my fault, I did trust Lineage-OS too much so I didn't think of backing-up. I didn't believe something like this could happen.

chaos_prevails said:
I did trust Lineage-OS too much so I didn't think of backing-up. I didn't believe something like this could happen.
Click to expand...
Click to collapse
You probably already realize this, at this point. But there is no such thing as an OS (on any device) that is so secure or stable, that backing up your data is not necessary. Even regardless of OS, memory corruption and data loss can happen for any number of reasons. Golden rule: If your data is important to you, back it up.

Of course, I know.
I took the loss of all data as opportunity to flash newest modem, CSC, and PDA firmware via latest stock-rom, and then re-flashed latest Lineage OS again. This time, it didn't factory reset my phone with encryption. Don't know if that had anything to do with my old firmware (I had G900FDXXS1CPK2 installed when factory reset-with-encryption happened).
Beside, I was lucky as no other migration method to my new phone worked out except going via a old-school micro-sd card copy. I could undelete almost all pictures on it