Clone this wiki locally
SD Maids setup consists of a few steps where you are asked to grant SD Maid certain access and permissions. Some are mandatory, some are not.
Primary Storage Setup
Primary storage is only required on Android 6.0+ devices. It is necessary because the general read/write permission for public storage can only be aquired during runtime since Android 6.0. Granting these permissions is mandatory as otherwise SD Maid will not function (what good is SD Maid if it can't access any files). Although ROOT permission superseed any other permission, even on rooted devices it needs to be granted. Trying to skip this step or abort it will close SD Maid.
Secondary Storage Setup
Secondary storage setup is a step that is only available on Android 5.0+. It's purpose is to grant SD Maid read/write access to storage locations through the system built-in Android Storage Accessframework (SAF). Since Android 4.4 most devices no longer allow apps to write to the secondary storage (e.g. external/removable sdcards) and accessing sdcards through the SAF only works since 5.0. So sadly Android 4.4 users are out of luck. Anyways, if you reach this step, SD Maid will display a list of storage locations she would like to be granted access to.
- Tap an orange entry, remember the location it displays, e.g.
- In the new window open the drawer on the left and select the related storage entry
- If there is no entry for your sdcard, close the drawer again, tap the overflow menu button in the top right corner and select
Show sdcards, then repeat the previous step.
- After selecting the respective storage you should now see it's content in the main window.
- At the top right or bottom right corner, press the select button. You should now have returned to SD Maid and the previously orange entry is green. Rinse and repeat for every entry.
Documents window is empty (shows no sdcards)
On some devices the
Documents app that opens after pressing the orange entry is empty. No storage can be chosen despite having clicked
Show sdcards. This means that your ROM (not SD Maid) does not correctly recognize your extra storage. A few Galaxy (S7/Note4) have this issue, seems to depend on how/when the sdcard was setup.
- Make sure that the app
External Storage (com.android.externalstorage)has not been disabled.
- Formatting the sdcard. Possibly removing and reinserting the sdcard.
- Note: Currently due to a bug in SD Maid this skip can not be stepped. Update 4.1.4 will fix this soon (#352).
Activity not found
The activity through which you grant SD Maid access is part of the "Documents" app, specifically the app with the packagename
com.android.externalstorage. This should be available on any 5.0+ ROM as it is part of the Android Open Source Project (AOSP). If you are getting this error you or someone else modified the ROM such that this app is either not installed or disabled. To check for it's existance you can enable "Show system apps" and then search for the packagename using SD Maids AppControl tool.
- Check whether the app is disabled by default on your device. Some ROMs (common on MIUI ROMs) ship with these system apps disabled. It's usually possible to find the apps in the systems app list and enable them by hand.
- Ask the manufactor why his 5.0+ ROM is not Android CTS compliant.
Invalid storage / Invalid input
If you select the wrong storage location (or SD Maid is just not happy with the selection for any reason) you will see and error message and the entry will stay orange. In some cases it is possible that you selected the correct storage and it still said "Invalid" and didn't accept it. Reasons for that are usually related to your devices ROM (e.g. #312 or #231).
- In some cases removing, formatting and reinserting the sdcard helps (Known cases: Galaxy S7 edge).
- As a temporary solution you can permantly skip this step by choosing "Don't show again" from the overflow menu in the top right corner. If SD Maid v3 could acccess the storage previously, it should still be able to access it if you skip this step (e.g. on rooted devices).
"Documents has stopped"
Certain LG and Samsung ROMs (Android 5.0-5.1 afaik) had a bug where the documents app crashed if one or more storage entries had an empty name. The specific exception is something a long a nullpointer exception.
- Updating the ROM, in most cases Samsung and LG fixed this bug with an update.
- Inserting the SD Card into another device and giving it a name (e.g. computer/notebook).
Permissions don't survive reboots
Despite successfully granting storage access, after rebooting the procedure has to be repeated. This is an Android bug and known to happen on all devices up to Android 7.0 where SD Maid has been installed to secondary storage (e.g. sdcard). Also see #437.
- Move SD Maid back to internal storage
Binaries are extra files that SD Maid sets up on first run. These binaries are required for SD Maid to run. SD Maid itself has compatible binaries for the architectures X86, MIPS and ARM. Normally this all happens automatically and you don't have to do anything.
The busybox binary is a mandatory file that needs to be setup, if this is not possible SD Maid can not continue. It is usually located in
/data/data/eu.thedarken.sdm/files/busybox, but may also be placed in other location to circumvent root restrictions on specific ROMs (also see: binary status).
Cause: Faulty root setup
The most common reason for this error is a faulty root setup. SD Maid thinks it has root, but using it fails unexpectedly.
- Remove SD Maid (the unlocker can stay installed), check that the folder
/data/data/eu.thedarken.sdmis gone. Check that SD Maid is no longer visible in the SuperUser app. Reboot your device. Reinstall SD Maid.
- Reroot the device.
- Clear the data of the SuperUser application.
- Deny SD Maid root access, then restart the device, grant SD Maid root access.
- Switch the SuperUser application.
Cause: Security restrictions
Some ROMs, most commonly Samsung ROMs, employ stronger security measures such as KNOX. SD Maids own toolkit may not be sufficient to work around all restrictions. Due to the restrictions SD Maid might have root, and might have been able to setup the binary, but can not use all commands with root.
- Disable KNOX.
- Change SELinux to
permissive.* Try a different SuperUser application (e.g. SuperSU), which might offer better workarounds for specific security measures.
Cause: Permission issues
On both unrooted and rooted devices it is possible that directory permissions are so screwed up that it can not change or execute it's own files. This can happen during an update, reinstall, downgrade or any other case that interacts with a preexisting install.
- Clear data for SD Maid.
- Reinstall SD Maid.
Cause: Incompatible architecture
It's unlikely, but possible that your device has a cpu architecture for which SD Maid does not have a binary file (outside of ARM/MIPS/X86).
- Install a compatible binary into your system which SD Maid can access.
- Email SD Maids developer and ask if it possible to create a compatible binary.