LUKS Manager

399 reviews
Content rating
Screenshot image
Screenshot image
Screenshot image
Screenshot image
Screenshot image
Screenshot image
Screenshot image
Screenshot image

About this app

*** Note: Your device MUST be *ROOTED* for this work. It will not work on non-rooted devices! ***

LUKS Manager provides on-the-fly encryption (AES by default) to virtual folders on Android devices.

These virtual folders can be dynamically mounted, unmounted, created and deleted as needed. Similar to Truecrypt in functionality.

Note: Truecrypt and LUKS Manager volumes are not cross-compatible.

Note: Maximum volume size is limited by the filesystem it is created on. Most SD Cards are formatted as FAT32 and FAT32 only supports file sizes up to 4GB. This is a limitation of the filesystem not LUKS Manager. If you want volumes larger than 4GB you must create the volume on an EXT2/4 partition.

**** If the application does not work for you, please visit my forums and let me know! I'm just one person, I have one device I test on; simply telling me it doesn't work for you doesn't help me at all. ****

If you have any problems, questions, comments or concerns please visit my forums and speak up!

The Android device must:

* Be rooted *

* Have a kernel that supports secure dm-crypt modes (CONFIG_DM_CRYPT) and loopback devices

* Have BusyBox installed

* Have SuperUser installed

Most stock kernels do NOT work!

This package contains:

* A statically compiled and stripped version of cryptsetup for the ARM7 using the tools provided by The Guardian Project.

* A statically compiled and stripped version of mkdosfs from dosfstools package for the ARM7.

* A bash shell script called "luks" that does volume management.

* A native java app that provides a GUI interface to the luks script and a basic file explorer.

Complete Changelog:

Version 2.4
Fixed lockup when creating volumes with FAT support disabled.
Fixed text editor menu ordering.
Added support for Samsung preferences path.
Fixed false volume notifications on non-rooted phones.
Notification fixes when volumes are created, mounted and removed.
Removed time stamp on volume mount notifications.
Set minimum volume size to 3MB in luks script.
Improved volume unmount reporting.
Symbolic links to devices may be used as containers.
Modified the cut command to work with more versions of busybox.
Fixed a bug dealing with volume removal when launching the luks script manually.
Rewrote code sections due to moderate source corruption. *sigh*
About text changes and updates.

Version 2.3
Major rewrite to the luks shell script and GUI app to support user defined volume locations.
Encryption cipher and keysize are now user definable. (kernel support required)
Moved storage of volume information:
From: /mnt/sdcard/luks/.data
To: /data/data/com.nemesis2.luksmanager/.data
Prompts to upgrade if loop device files are found in SDCard .data directory.
Removed top level restriction on file explorer activity.
Default file system changed from EXT4 to EXT2.
FAT file system support now enabled by default.
Added volume mount and unmount desktop shortcuts.
Added notification when volumes are mounted. (Can be toggled off in preferences)
Added landscape support to the main and volume edit activities.
Added basic SDcard support to install binaries routine.
(Fixes java.lang.NullPointerException on binary install.)
Added toggle to disable binary hash checks on startup. This enables customized luks scripts and/or binaries.
Small fix to application initialization. (hopefully fixes odd reboot issue on some devices)
Attempts to unmount volumes on ACTION_SHUTDOWN and MEDIA_EJECT broadcasts.
Additional checks and error handling if no volumes exist.
Additional error handling in luks script during volume mounting and creation.
Added required BusyBox applet checks on startup.
About Dialog additions / changes.
Small text changes (formatting and typo fixes).

Version 2.2
Recompiled lm.cryptsetup binary under android-ndk-r6b.
Hopefully this will stop segfaults on various devices.

Updated on
May 19, 2012

Data safety

Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time.
No data shared with third parties
Learn more about how developers declare sharing
No data collected
Learn more about how developers declare collection

Ratings and reviews

373 reviews
A Google user
December 27, 2013
This is an excellent program that provides the on the fly encryption it advertizes. However, getting it set up to work properly is, unfortunately quite difficult. It took me 3 or 4 install, setup, test, followed by complete uninstall, cycles before I got it working properly. Setting up busybox properly BEFORE installing Luks is very important. But once you get it working, it works properly. I gave only 4 stars because I think it lacks an important feature, a timeout for auto dismount.
10 people found this review helpful
Did you find this helpful?
A Google user
January 29, 2014
Love it. Well done. SGS2 Running PAC (4.2.2). would be 5 stars if a feature to mount preexisting containers was available. Anyone seeing issues with RNG on SGS2 use stweaks to disable frandom. Others may benefit using PRNG generator in PimpMyROM.
4 people found this review helpful
Did you find this helpful?
A Google user
September 22, 2012
After years of Windows phones, I just switched to an Android, and it was not a fun transition. Yours was one of the few that was compatible with the data I was using, and while a little tricky to set up, I was so glad to have it. Thank you for providing it. I noticed some people having some problems with trying to use LUKS and FreeOTFE, so I thought I'd throw in some things I found helpful while I stumbled my way learning how to make this work. The volume file has to be created in LUKS first, not in FreeOTFE. It cannot exceed 3999 MB, and has to be FAT32. This is not a limitation of LUKS or FreeOTFE, but a limitation of Windows. See the FreeOTFE FAQ. Before accessing the volume file from FreeOTFE, make sure your volume has been dismounted from LUKS, and USB debugging has been disabled. Connect as a USB Mass Storage Device. Open the volume from the FreeOTFE console, rather than double clicking on the volume file. When your done doing whatever it is you want to have done, dismount the volume file properly from FreeOTFE. Remount the file using LUKS. Be paranoid. Remember your password. Backup your volume as a whole, or a regular encrypted FreeOTFE volume on your computer.
3 people found this review helpful
Did you find this helpful?

What's new

Maintenance release: Bug fixes and small changes.
Please see the changelog for details.