Skip to main content
Version: next

Packet Format

ADB protocol is a bi-directional, packet-oriented protocol. Each packet has a fixed-sized header and an optional, variable-sized payload.

Because it is originally implemented in C for Linux, all multi-byte fields are in little-endian, and all strings are in UTF-8 encoding.

On Android 8 and below, it used char * for string handling, so null terminators are required. Now it’s transitioning to std::string, which doesn't require null-terminators. But not all places has been changed, and for backward compatibility, adding null-terminators are still recommended.

Each packet contains following fields:

Byte OffsetTypeFieldDescription
0char[4]commandPacket type
4in32arg0Meaning defined by each packet type
8in32arg1Meaning defined by each packet type
12uint32payloadLengthLength of payload, in bytes
16uint32checksumChecksum for verify data integrity
20uint32magicShould equal to command ^ 0xFFFFFFFF
24byte[payloadLength]payloadMeaning defined by each packet type

Command

The command field consists of four ASCII characters.

For example, "CNXN" packets' command is [0x43, 0x4e, 0x58, 0x4e], or 0x4e584e43 in Hex (Hex strings are big-endian).

arg0/arg1

Two integer parameters for the command.

Checksum

Checksum is calculated by adding up all bytes in payload.

For example, when the payload is [0x01, 0x02, 0x03], the checksum is 0x01 + 0x02 + 0x03 = 0x00000006.