The malicious utilization of native codes such as C and C++ against Android can be dated as far back as 2010. The native codes were implemented in Android root attacks such as RageAgainstTheCage and GingerMaster in 2010 and 2011 respectively. Malicious applications exploited these native binaries to gain root access on the infected devices and ensure the infection always present. Analysis of the native binaries was an easy task at that time as the source code could be accessed online. Along with the improvement of Android NDK, nowadays native binary in malicious applications has sophisticated functionalities and become much more complicated. The first Android bootkit, OldBoot, discovered at the beginning of this year, includes two native binaries with capability of executing commands with root permission, sending SMS, and providing C&C services. Android packers and obfuscation tools such as Bangcle and ApkProtect take advantage of binaries to decrypt and load payload in runtime. Also, SophosLabs has recorded and detected more and more Android malware embedded with multi-function native binaries. However, there are no adequate documents, tools and systems for malware researchers to analyze the functionalities and behaviors of Android native binary. As a result, this paper will demonstrate a detailed analysis of native binary in the samples above and will further cover the following topics: What does native binary look like in ARM assembly language? Android NDK reverse engineering on these native malware samples in static analysis Debugging Android native malware samples in dynamic analysis by using IDA pro and GDB Discuss the basic idea and implementation of packing Android native binary