Hi,
I bought the Samsung Galaxy S5 and the fingerprint reader works reasonably well (as in it works, nothing in comparison to apple though, so don't buy it for the fingerprint reader ) for unlocking the screen...
However its a work requirement that my phone has full device encryption, as phones are regularly stolen where I travel.... it seems when I enable encryption I lose the ability to use the fingerprint reader to unlock the phone .... I bought this hoping that I could avoid having to type in my complex password just to unlock the screen, as I got so tired of doing that with my S2
Is there any mods to enable finger print reader screen unlock + full device encryption at boot time for the Galaxy S5 yet? ... I saw some references to pattern unlock / pin with device encryption... but I would think the fingerprint reader is different...
Thanks!
S5 Full disk encryption with fingerprint unlock
I also have this question. I believe on the Nexus 5 it at leasts lets you use face unlock with full device encryption. And I read on one article that you should be able to do this but i do not think the author actually tried this. I will say from my own personal experience that you can infact decrypt the device after encrypting it without doing a complete wipe of the device and you can restore the use of fingerprints to unlock your phone. It seems like for security minded people this would be a great feature but if it is unable to be used with full device encryption it seems a little pointless to me. Being forced to use a PIN or password to use encryption is a big pain point for android users who want some type of security.
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
androidpleb said:
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
Click to expand...
Click to collapse
I am having the same pain, as I use my S5 for BYOD.
It makes no sense when you can use fingerprint to make payments with paypal but not unlocking the phone when it is encrypted.
Hope Samsung can enable this feature in next update.
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
sorphin said:
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
Click to expand...
Click to collapse
I can't believe that the fingerprint sensor can't be used if encryption is enabled whatsoever. I could understand the iPhone model, requiring a pin before a fingerprint can be used, but by disabling fingerprint lockscreen, boot unlock, and SD unlock, the fingerprint sensor is now wholly useless for convenience.
It's too trivial to extract data from an unencrypted Android. By not supporting encryption with a measure of covenieve, I don't see the point in including a fingerprint sensor whatsoever given the current software limitations.
Please, someone, figure out what sqlite/settings need to be changed so we can make decent use of our phones fingerprint sensor.
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Boot Loop
fabiokino said:
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Click to expand...
Click to collapse
I get samsung boot loop using the above instructions
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
Hi guys! Did someone try this solution? I unfortunately have the same issue and unlock my device each time make me crazy!
Thanks in advance.
Same problem
I purchased a Galaxy S5 and I have the same problem, unfortunately I cannot root my phone due to security policies in my company. :crying:
I hope Samsung will solve the issue. :fingers-crossed:
Have anyone contacted to Samsung Support Center?
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
What is the consequence of boot loop if you are using stock boot loader? Odin mode required to recover? Something less drastic? What device model are you using?
I found a possible solution that involves deactivating SuperSU and running encryption from there. Still investigating. I am thinking that the solution from @fabiokino will work in this case too.
I'm curious about this aswell.
Doesn't anyone know a working solution?...
It is really frustrating the very least. I can't believe there isn't a way (or if there is, a guide) to do this (with or without root access).
I have also heard it is doable on the Note 4. See this post for example http://forum.xda-developers.com/showpost.php?p=57103664&postcount=7.
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
How?
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Nice to see this, hope it will work on my Galaxy tab S too
Did you see this?
https://www.jethrocarr.com/2013/12/29/encrypting-disk-on-android-4/
GermanDoerksen said:
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
Click to expand...
Click to collapse
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Joker87 said:
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Click to expand...
Click to collapse
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
GermanDoerksen said:
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
Click to expand...
Click to collapse
You could root then unroot it after you have encrypted it
Joker87 said:
You could root then unroot it after you have encrypted it
Click to expand...
Click to collapse
you're right... plus it's not really the "rooting" process that makes it slow, it's installing another ROM. Having a rooted phone doesn't necessarily have any performance impact... just opens up a few things for me. Interesting. Thanks! Unfortunately I've already encrypted so now I have to find that thread about how to decrypt lol.
Thanks!
Hello all!
Glad I can report that the towelroot exploit worked successfully on my Verizon Samsung Galaxy S5 phone.
I'm a noob to Android devices, but I think they are awesome
I've spent most the day reading up on Android backup and recovery, differences between rooting and unlocking the bootloader, and I have a couple of questions relating to these topics:
1) I've rooted my Samsung Galaxy S5, and, in the event that I accidentally loaded a virus on my phone, or seriously messed something up with my root access, I'd like to have a way out of it. I've been reading up on the Android Recovery Mode: Wipe Data/factory reset. My question is this: Is it still okay to use this feature after I've rooted my ROM using towelroot? Also, if I use this feature, will it also completely re-install system software (like a Win 7 Reinstall)? Or is this just deleting some user data and leaving the once upon a time read only folders alone?
If method one mentioned above isn't a full OS restore, I think this is my other option...
2) Since I've rooted my phone with towelroot, I know that my bootloader is still locked. I know that another backup option is to use CWM to do a custom backup/recovery, however, I know that unlocking the bootloader right now may not be possible. I can't find any already existing threads relevant to Verizon Galaxy S5 bootloader unlocking since towelroot has been released released, however, I have stumbled upon this website which mentions my phone in the list: (I can't post links yet, please google "samsung galaxy s5 cwm phizl", and click on the second link. What do you guys think of this guide, do you think this will actually work for the unlocked Verizon Galaxy S5?
Thank's for any help with this.
Does this question stump everyone?
If you do a wipe it goes back to how it was when you first installed the rom/ first boot.
shredfast said:
I'd like to have a way out of it. I've been reading up on the Android Recovery Mode: Wipe Data/factory reset.
Click to expand...
Click to collapse
This is oversimplified, but the files on your phone are more or less organized like this -
1. User settings, installed apps (data partition) - this is what a factory data reset would erase.
2. System files (most of them) - these read only files don't normally change unless you get an OTA firmware update. If you accidentally delete or somehow corrupt system files, you can reinstall the firmware to fix these. A custom ROM (if your bootloader was unlocked) would replace the files here.
3. Cache. These are temporary files. Some problems can be fixed by deleting these. If deleted, your phone will rebuild the cache when it boots.
4. SDcard. Built in, internal storage space for user files, downloads, etc. If you have a physical SD card, that is seperate and referred to as the external or secondary SD card.
5. Other stuff e.g. the bootloader, modem, etc.
A 100% backup is often referred to as a "Nandroid". Meaning that you backup the entire memory (NAND). You can only do that properly with a custom recovery like TWRP or CWM. The next closest thing would be an app like Titanium Pro.
The system data reset will only default the user settings (data partition). It won't remove most user files (internal SD card) or touch the read only system files (system partition).
I don't know what your second question really pertains to. You should have described it fully, rather than try to get us to replicate your Google search. I'll just say that it's highly unlikely that anyone will figure out how to unlock the Verizon bootloader anytime soon.
Verizon has an unlocked Developer model phone, but it is handicapped by poor firmware updates. If you want the advantages of an unlocked bootloader, change carriers. Most carriers do not lock the S5 bootloader. Just ATT, Verizon and a few US CDMA carriers.
Because your bootloader is locked, you can't use a real custom kernel or recovery. But they can be emulated with Safestrap.
.
Hi,
Lately, I got a Marshmallow update for my Moto X Play to which I upgraded and as I wasn't quite aware of the Encryption Policy for the same, I tried mixing my 64 GB Samsung MicroSD with my internal storage. It worked fine until I started having problems using the new Marshmallow upgrade. I decided to downgrade, did not bothered about decrypting the card before downgrading.
As soon as I downgraded the device to Lollipop, I found that I was no longer able to use the MicroSD in the same way I used to do it earlier. It was write protected and I was not able to decrypt in any way.
Googling didn't quite helped, and it looks like very few people have had similar problem.
Anyone having same issue? And any solution to this?
I think if you reformat the card you can start using it again, but you will lose all data.
Hello, I wanted to root my phone, but in the middle of the process the phone didn't want to load up. It took like 10 mins, so I restarted it and it didn't load too. I think it was caused by Android 6.0 or too low memory. However, this would still be ok, I would wipe the memory and stuff, but I cant access the recovery which enables me to do so. I can only access eRecovery, but there are only 3 options: Reboot, Get update from network (doesn't work), and Shutdown. Any suggestions how to fix it? This is a very good phone and I can't afford to lose it (I'm a student, don't have enough money to buy a new one). Thank you for your answers (hopefully ).
Lyincake said:
Hello, I wanted to root my phone, but in the middle of the process the phone didn't want to load up. It took like 10 mins, so I restarted it and it didn't load too. I think it was caused by Android 6.0 or too low memory. However, this would still be ok, I would wipe the memory and stuff, but I cant access the recovery which enables me to do so. I can only access eRecovery, but there are only 3 options: Reboot, Get update from network (doesn't work), and Shutdown. Any suggestions how to fix it? This is a very good phone and I can't afford to lose it (I'm a student, don't have enough money to buy a new one). Thank you for your answers (hopefully ).
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Chapter 3 and 4 may be helpful in your situation, I personally don't even have unlocked bootloader so I won't be of any assistance but this thread might help you.
Hello All,
I have a Galaxy S5 that I must keep encrypted because it is a work phone and my workplace requires that it be encrypted.
I recently tried to add an SD Card (tried 3 different sizes and 3 different brands) and got the dreaded cannot mount cannot encrypt error loop.
I searched the net and found numerous complaints that all seem to point to the Android OS rather than a specific phone. I am using 6.0.1 on my phone.
I did not find any solution posted anywhere.
I am wondering though, has anyone tried to decrypt the phone, unlock the screen, add the sd card, then re-lock the screen, and re-encypt the phone ?
I did not see anyone post anywhere that they tried this.
Any helpful hints appreciated.
It Is Not Fixed
I have tried every method I have found from searches including ones from later Samsung unit forums and none of them work.
The only thing I have not tried is factory reset because it is a work phone and it will blow away all of the work apps and getting them restored will take weeks.
I cannot even try to decrypt the phone because it is Marshmallow 6.0.1 and decrypt does not work. You have to factory reset the phone to start all over.
I have decided to leave the micro sd card in the phone in the hopes that next OTA update will see it and apply some fix to allow it to work.
This Encyption stuff is really a doomsday. I have an identical phone slightly older but still a Samsung Galaxy S5 with Marshmallow 6.0.1 unencrypted and it takes the micro SD card with no problems and works great.
IF YOU DO NOT HAVE TO ENCRYPT YOUR PHONE, JUST DO NOT!!!
The encryption does not really work anyway. If you connect your phone to a pc and enter your password for the lock screen, all of your internal files are visible once you tap file transfer from the notification pull down.
So encryption does nothing beyond the lock screen. If someone can bust your lock screen password, they've got everything.