| Device | Firmware Versions (ftab.bin) |
|---|---|
| AirPods (2nd generation) | 3E751, 2C54, 1A671, 4E71, 3A283, 2D15, 6F21, 6A326, 6A321, 1A691, 2A364, 5B58, 6A300, 5E135, 5E133, 5B59, 1A673, 4C165, 4A400 |
| AirPods (3rd generation) | 4E71, 6F21, 6A326, 6A321, 6A317, 4C170, 4B66, 4B61, 5B58, 6A300, 5E135, 5E133, 5B59, 4C165 |
| AirPods Pro (1st generation) | 3E751, 2C54, 2B588, 4E71, 3A283, 2D15, 6F21, 6A326, 6A321, 4A402, 2B584, 5B58, 6A300, 5E135, 5E133, 5B59, 2D27, 4C165, 4A400 |
| AirPods Pro (2nd generation) | 5B58, 5E135, 5E133, 5A377 |
| AirPods Max | 3E756, 4E71, 7E101, 7E108, 3C39, 6F21, 6A326, 5B58, 6A300, 5E135, 7E99, 5E133, 5B59, 6F25, 6A324, 3C16, 6A325, 4C165, 4A400 |
These firmware versions use UARP Super Binaries, which require uarp-dump to extract the FTAB file from the UARP Super Binary before processing with ftab-dump:
| Device | UARP Versions |
|---|---|
| AirPods (4th generation) | 7B20, 7B19, 7A304, 7E93, 8A356, 8A358 |
| AirPods Pro (2nd generation) | 7B21, 7B19, 7E93, 6A303 [1], [2], [3], 7A302, 7A305 [1], [2], [3], 6A305 [1], [2], [3], 6B34 [1], [2], [3], 6B32 [1], [2], [3], 6F8 [1], [2], [3], 6F7 [1], [2], [3], 5B58, 5E135, 6A301, 5E133, 5A377, 8A356 [1], [2], [3], 8A358 [1], [2], [3], 7A294 |
| AirPods Pro (3rd generation) | 8A357, 8A358 |
$ cargo install ftab-dump
$ ftab-dump -v ftab.bin -o ftab_dumpftab-dump [OPTIONS] <FTAB_FILE>
-o, --outdir <DIR> Output directory (default: ftab_dump)
-f, --force Overwrite into an existing, non-empty directory
-v, --verbose List tags and sizes as they are written
--dump-manifest Also write the manifest ("ticket") block to manifest.bin
--lenient Reproduce the device's tolerant reader: clamp payloads
and the manifest that run past the end of the file to
the bytes actually present (with warnings) instead of
rejecting the image
By default parsing is strict: a payload or manifest whose declared range falls
outside the file, or a payload that overlaps the header/table, aborts with a
clear error so truncated or corrupt images are never silently half-extracted.
--lenient mirrors the on-device reader exactly. Subfile filenames come from
the 4-character tag and are sanitised against path traversal (collisions and
unsafe tags fall back to an 8-hex-digit name).
The layout and validation rules are verified against Apple's on-device reader
UARPRTKitFTAB and cross-checked with B1N4R1 B01's rkos.py. All integers are
little-endian.
The 48-byte (0x30) header carries the manifest offset/length at 0x10/0x14,
the 8-byte magic rkosftab / RKOSFTAB at 0x20, and the subfile count at
0x28. It is followed by that many 16-byte metadata records starting at 0x30,
each holding a 4CC tag, a payload offset, a payload length, and four reserved
bytes. Payloads (and the optional manifest) are stored at their absolute
offsets.
- B1N4R1 B01 (Twitter - Github)
- Nikias Bassen of the idevicerestore project
If you intend to analyze rkos files, note that the AirPods Pro 1, 2 and 3 use an Arm Cortex-M4 32-bit RISC CPU with VFPv4 and ThumbV2 instructions using the ARMv7-M architecture with a little endian byte sex.
~~ MIT License ~~
Copyright (c) 2020 - 2025 Kenan Sulayman
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.