English

Encrypt phone with FairPhone Open OS

Hey @AnotherElk,

thanks for the fast reply.

You are probably right such a list might make sense to speed up all the necessary reinstall and reconfiguration steps. I will create one before I will try to encrypt my device.

At least I’m practiced in backup and recovery stuff, because of the last problems I had. ^^

So some addtional questions:

  • What is the correct amount 4K blocks? And in addition how to ensure that there is enough space in the encryption folder? I thought this is somehow equal for all FP2s?! (right now this procedure feels a bit hacky to me)
  • So you don’t use Snooperstopper? As my encryption password will probably be some kind of dice-ware near strong password I would really like to set a separarte simpler screen unlock password.

Today I will not going todo anything as I’m “on the rush” :wink:

I don’t know … I quickly tried to run the quoted e2fsck command on my phone to see whether its output gives a hint, but even with everything unmounted it just reported something is in use, perhaps because of the active encryption, no idea.
So I have no way of knowing whether the 4K block number given in the quoted resize2fs command does work for every Fairphone. I would try the TWRP “Resize” first and have a look whether all the data is still there and whether encryption works then … that would be nice :slight_smile: .

If that doesn’t work, I would of course try the more complicated stuff and confront losing my data and perhaps having to reinstall.

By the way … there is a nice bonus if you decide to go the 100% clean way, meaning to wipe everything, do the resize, install the OS from scratch and as soon as it successfully booted start the encryption … because there is almost no data at this point, encrypting will be lightning fast.
Of course you have to invest the time saved by that in reinstalling Apps and re-setting all those important settings :slight_smile: .

No, I can’t help with that, sorry.

Yes, for a long time already I use FP Open OS with encryption, pattern lock screen and a separate alphanumeric password which I installed with Snooper Stopper. I never had a problem with wrong partition size, I think.

Thanks @m4lvin for your reply.

So maybe I will just give it a try without resizing stuff in advance. (of course I will still take backups :wink: )

Can you have a short look to this thread: Encryption password does not work anymore for normal boot but for twrp (changed with snooperstopper)
I (as well as @freibadschwimmer ) ran into a problem while using Snooperstopper and I’m afraid that this will happen again. Not sure if this is a specific problem while resetting encryption password with Snooperstopper.

Eventually encryption password should only be set and changed via encryption menu of the OS. Snooperstopper should only be used to set a separate screen unlock password/pattern. Just a theory.

I saw the other thread before but don’t know how to help you because for me Snooperstopper did not generate this or any other problem.

I think it is the other way round: The separate password in SnooperStopper is for the encryption and the PIN or pattern for unlock is managed by android. I don’t have a separate encryption menu where I could change the encryption password.

Maybe first try encrypting and reboot a few times and also check that you can mount it in TWRP, and only after that install and use SnooperStopper?

Yes, you are right I mixed that up.

Ok, I will give it a try as soon as I have enough time for eventual troubleshooting. I will let you guys know the result.

For the record, I just got a brand new FP2. After the initial boot in the normal OS, I did the OTA install of FP Open. Then after making sure things worked, I launched the encryption process. Everything proceeded smoothly, and it’s asking me for a password before booting.

1 Like

Hello,
I got a new FP 2 and have the same problem after changing back from FP Open to the Google software. I am trying since days to solve the problem. Therefore, I read with interest a lot of info. Many thanks! But much to my regret the instruction to resize the data partition does not work.

As I am a Fairphone newcomer, sorry for the silly questions:

I would also like to test the other resizing as indicated above :
quote
e2fsck -y -f /dev/block/mmcblk0p20
resize2fs /dev/block/mmcblk0p20 6790139
unquote

But where in TWRP can i do it?

Thanks in anticipation.

Advanced -> Terminal

1 Like

It seemed to be successful because I got the info:
“The filesystem on /dev/block/mmcblk0p20 is now 6790139 blocks long”

After reboot the encryption, however, did not yet work.
Do I also have to go back to factory settings?
Via TWRP?
If via TWRP please give me a short info whether only the data partition is concerned.

Many thanks.

If you’re willing to start from scratch (you will lose your data on the phone), you might as well do it right and wipe the whole phone for a really clean new install …

Some findings about android device encryption:

  • A Factory data reset (via Settings --> Backup & reset) does not remove device encryption.
  • A clean way to remove device encryption: TWRP -> Wipe -> Format Data
  • When you have a TWRP-backup of an encrypted userdata partition, it is not possible to restore to an unencrypted userdata partition (boot loop). Workaround: 1. Factory data reset 2. Encrypt phone via (Settings -> Security) 3. Restore your TWRP-backup of userdata via TWRP.

Tested with twrp-3.1.1-1-fp2.img and LineageOS.

5 Likes

Many thanks to all for the info concerning failed encryption. I tried everything to get my phone encrypted because this is an essential factor for me since one of my phones was stolen some time ago.
I tried resizing, wiping, factory reset etc. but no success. Then I contacted Fairphone Support and also tried their advice.
Also no success! Frankly speaking I was frustrated and used the phone without encryption.

Today I found the solution occasionally. I had to buy a new micro SD card because I wanted to store my complete music collection on the card. I bought a 64 GB SanDisk card, formated it under Linux Ubuntu with FAT, inserted it and tried to encrypt.
It worked!!! My Open Fairphone is now encrypted. I do not know why it works, but I am completely happy!

1 Like

Hello.

After more than 3 hours of reading forum, flashing TWRP 3.2.1, attempts to reach recovery with Volume DOWN instead of Volume UP (cause I did not read properly) I now have:

root@FP2:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/userdata
lrwxrwxrwx root     root              1970-01-01 01:56 userdata -> /dev/block/mmcblk0p20
root@FP2:/ # tune2fs -l /dev/block/mmcblk0p20 | grep "Block count"             
Block count:              6798327

Which is four 4 KiB blocks less than:

root@FP2:/ # fdisk -l /dev/block/mmcblk0 | grep userdata                       
  20         6684672        61071326       25.9G   0700  userdata

irb(main):004:0> ( 61071326 - 6684672 ) / 8
=> 6798331

Yet still on trying to encrypt the device it still just reboots.

I then lowered the number of 4k blocks to 6798000, but it still just reboots without encrypting.

Currently there is no SD card in the device.

What else to try?

Are you aware whether Fairphone has any intention to fix up this feature? This just worked out of the box with Fairphone 1.

How I do get any exact error messages on what actually fails here? They are certainly not displayed on the screen of the phone.

Additional note: In case you have no SD card installed, you also need to umount /sdcard in order to be able to resize this partition. At least it was mounted to this partition as well here.

1 Like

@helios Have you read this topic? If you have a FP2 with the new camera module, some people (including me) succeeded with the encryption by temporarily removing the camera module.

1 Like

Thanks fair2fair. No, I did not find this. I will reply there, as I am stuck with how to do that.

Just as an update to this thread here: Removing the camera module did the trick for me. I then first used the twrp resize menu option for the data partition and then triggered the encryption. It completed in a few minutes with I think about two reboots.

2 Likes

For me, albeit using Lineage, removing the new back camera (the small module) was enough to get it to encrypt. Didn’t need to remove the new top bar/front camera.

1 Like

Is it normal, that booting the encrypted phone becomes extremely slow?

I would say, my phone needs more than twice the time than before encrypting…

PS: Yes, removing the camera was the solution for me, too.

Yes, booting the phone takes significantly longer when encrypted.