Need help with android_aircrack?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

266 Stars 77 Forks Other 12 Commits 2 Opened issues


Aircrack-ng command-line for Android. Binaries & source.

Services available


Need anything else?

Contributors list

# 265,374
11 commits


Aircrack-ng for Android

This repository is a port of the Aircrack-ng 1.2-beta2 suite (except scripts) for Android. It works directly on top of Android. This port is done by KrisWebDev and is not "affiliated" with the team.


Aircrack-ng is an 802.11 WEP and WPA-PSK keys cracking program that can recover keys once enough data packets have been captured. It implements the standard FMS attack along with some optimizations like KoreK attacks, as well as the PTW attack, thus making the attack much faster compared to other WEP cracking tools.

Running Aircrack-ng on Android (precompiled)


  1. Device with WiFi chipset, firmware & driver that support monitor-mode
    • As of early 2016, only mass-market compatible devices are thoses having dedicated Broadcom 4329 or Broadcom 4330 WiFi chipsets (Samsung Galaxy S1, Samsung Galaxy S2, Nexus 7, Huawei Honor). Bcmon team has developed firmware and driver hacks for these chipsets. More recent devices have WiFi digital signal processed by the ARM CPU (Qualcomm or Samsung) and there is no publicily known monitor mode hacks for these devices at this time.
    • Otherwise, go look for USB WiFi adapter known to provide WiFi monitor-mode and injection support on Android.
  2. Wireless extensions enabled in Android kernel
    • That's normally bundled with the loaders/kernels below.
  3. Monitor-mode firmware & driver loader
    • Broadcom 4329: Bcmon won't load on CyanogenMod > v7 due to the move from bcm4329 driver to bcmdhd. For Galaxy S1, use PwnAir on a KitKat ROM (or port the open source PwnAir kernel to more recent ROM following PwnAir kernel build instructions at the end of the XDA thread).
    • Broadcom 4330: Use bcmon app (not maintained anymore by their owners) to load the monitor-mode firmware and driver.
    • USB WiFi adapter that supports monitor-mode: This completely depends on your USB WiFi adapter and is out of scope of this README. You will need to find and build the driver, along with your ROM kernel, from source. Otherwise you would probably face the magic version mismatch issue. As Android kernel is a Linux kernel afterall, you should succeed in compiling the driver from the Linux driver source. Either find a nice HowTo for compiling your USB WiFi adapter driver on a defined Android ROM, or struggle with the driver build guide of your Android ROM. Note that some guides use a chrooted Ubuntu or Kali as an alternative to building a pure Android driver.
  4. Android SDK platform-tools installed on your PC (for install)



Check your wireless interface status (should be in "Mode: Monitor"):

adb root
adb shell iwconfig

Check Airodump is working:

adb shell airodump-ng eth0

Provided your wireless interface is eth0.

If it is working, then check the Aircrack documentation for HowTo.

Building Aircrack-ng on Android

There is no need to build Aircrack-ng yourself unless you're paranoïd about the binaries I provide, or unless you want to change/upgrade the Aircrack-ng code. Android Aircrack-ng binaries should work on any Android phone. The hard part about running Aircrack-ng on Android is to load a monitor-mode WiFi firmware & driver that works for your phone or USB WiFi adapter: that's where you should focus your efforts instead.


Firmware/driver pre-requisite

Same pre-requisites applies as for Running. You still need to have a monitor-mode WiFi kernel/driver installed on your Android system prior to using Aicrack for Android.

Preparing the build environment

Instructions are made for CyanogenMod platform build system, as it includes all the necessary libraries and tools.

Warning: Compilation has not been tested on Android NDK system build alone, without all the platform tools. Building only with Android NDK instead of CyanogenMod platform build system would require you to have have at least the following sources located in an folder called "external" (check * Aircrack-ng for Android (android_aircrack) * OpenSSL development package (openssl) * SQLite development package

>= 3.3.17
(3.6.X version or better is recommended):
* zlib (or change the flags to use -LDLIB)
  • Follow Cyanogenmod build guide for your device but stop before "brunch". You need several GB of disk space and a good Internet connection.
  • Copy this Aircrack-ng for Android repository content to a directory named "aircrack-ng" in CyanogenMod source root "external" folder.

Building wireless tools binaries

If you also want to build the Android wireless tools instead of using the Android wireless tools precompiled binaries, then download and put the Android wireless tools in CyanogenMod "external" folder and run from the CM source root (

. build/
breakfast galaxysmtd
export USE_CCACHE=1
mka iwconfig
mka iwpriv
adb root
adb remount
adb push $OUT/system/bin/iwconfig /system/xbin/
adb push $OUT/system/bin/iwpriv /system/xbin/

And so on for all tools listed in Android wireless tools Replace galaxysmtd by your device CyanogenMod name.

Building Aicrack-ng binaries for Android

The following commands have to be run from the CyanogenMod android source directory (croot).

  • Edit

    . external/aircrack-ng/
    and replace "galaxysmtd" with your device CyanogenMod code, should it have any impact at all.
  • Compilation:

    . external/aircrack-ng/
  • Push binaries to the device (through adb, USB debugging mode must be enabled on the device):

    . external/aircrack-ng/
  • Re-compile and push:

    mmmp external/aircrack-ng
  • Checking (provided that monitor mode is enabled on your device and that interface name is eth0):

    adb shell airodump-ng eth0


Aircrack-ng official documentation

Documentation, tutorials, ... can be found on See also manpages and the forum.

Aircrack-ng for Android

Support Aircrack-ng for Android is done on XDA PwnAir thread Q&A section or on the GitHub repo.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.