Logical and File-System Acquisition
Logical acquisition retrieves data from a mobile device through vendor-provided APIs, presenting files and records without direct access to raw storage. File-system extraction goes one step further, capturing the directory tree and accessible file content without requiring the low-level chip access that physical imaging demands.
Last updated:
Logical acquisition is the process of extracting data from a mobile device by communicating through the operating system's own application programming interfaces rather than bypassing them. The device remains operational, the examiner sends structured requests through a synchronisation protocol or backup API, and the device returns a defined set of files, databases, and records. The method is fast, non-destructive, and widely supported by commercial forensic tools, but it is bounded by what the vendor API is willing to expose: unallocated storage, deleted records outside a trash folder, and data in encrypted containers the OS does not surface are all outside its reach.
File-system extraction operates at a layer deeper than a logical pull. Rather than requesting only the records an API packages for backup, the examiner mounts the device's file system or uses a privileged API to traverse the directory tree directly, retrieving app containers, cache files, databases, and configuration files as they exist on the storage medium. The result is richer than a logical set and does not require the hardware disassembly that physical imaging or chip-off demand. However, it still cannot read unallocated sectors, so carving deleted files from free space remains impossible without a lower-level image.
Choosing between logical and file-system extraction is a practical judgment that balances the investigative need, the device's locked or unlocked state, the legal authority available, and the risk of altering evidence. Both methods sit between the unintrusive quick-look at cloud backups and the invasive physical image, and understanding their precise scope is essential before any acquisition decision is made. Investigators in the United States work within the Electronic Communications Privacy Act and device-specific case law; those in the United Kingdom apply the Police and Criminal Evidence Act 1984 and the Investigatory Powers Act 2016; in India, the Bharatiya Nagarik Suraksha Sanhita 2023 governs seizure procedure; and the EU's e-Evidence Regulation shapes cross-border requests.
By the end of this topic you will be able to:
- Describe how logical acquisition operates through vendor APIs and identify the data categories it can and cannot return.
- Explain how file-system extraction differs from logical acquisition and what additional evidence it can surface.
- Compare the scope, prerequisites, and limitations of the two methods using a structured framework.
- Identify the main tools used for each method and explain what distinguishes their approaches.
- Apply acquisition method selection criteria to a scenario involving a locked or partially trusted device.
- Logical acquisition
- Extraction of mobile device data through the operating system's own synchronisation or backup API. Returns a structured set of files and records the OS is willing to share, without accessing raw storage or unallocated space.
- File-system extraction
- A deeper form of extraction that retrieves the full accessible directory tree by mounting the file system or using a privileged API layer, yielding app containers and cache files beyond the backup API scope but still excluding unallocated sectors.
- iTunes backup protocol
- Apple's proprietary protocol for transferring device data to a computer. Used by forensic tools to conduct logical acquisition of iOS devices; backup files are stored in a structured format and may be encrypted with a user-set password.
- Android Debug Bridge (ADB)
- A command-line tool included in the Android SDK that allows communication with an Android device over USB or Wi-Fi. Used for logical and file-system extraction when USB debugging is enabled; higher-privilege adb commands require root access.
- Trust relationship (iOS)
- The pairing between an iOS device and a computer established when the user taps 'Trust' after connecting. A forensic logical or file-system extraction via the backup API requires a trust relationship; without it, only minimal data is accessible.
- AFC (Apple File Conduit)
- The iOS service that exposes the media partition for file transfer during synchronisation. In standard form it only surfaces the media partition; on jailbroken devices, AFC2 exposes the full file system, enabling file-system acquisition.
How logical acquisition works
Logical acquisition communicates with the device through an interface the manufacturer provides. On iOS devices, the primary channel is the same protocol iTunes uses to create backups: the examiner connects the device over USB, establishes a trust relationship using a stored pairing record or by prompting the user, and instructs the backup service to transfer a defined set of data. The backup package includes contacts, call history, SMS and iMessage records, photos in the camera roll, application data for apps that participate in the backup, health records, and browser history. The device itself controls what enters the package.
On Android devices, the equivalent path is the ADB backup command, which requests the system to produce a compressed archive of application data. Google also provides the Android Backup Service, which works over the network rather than USB. Both approaches return what the operating system and individual application backup policies permit. Applications that have set the android:allowBackup flag to false are excluded. System partitions, the bootloader, and unallocated storage are never included.
The primary advantage of logical acquisition is that it requires no special hardware, no device modification, and no exploit. Commercial tools such as Cellebrite UFED, MSAB XRY, and Magnet AXIOM automate the process and parse the backup into browsable report formats. The primary limitation is that the method returns only what the vendor allows: encrypted application containers, system databases outside the backup scope, and any data deleted from live records are not included.
How file-system extraction works
File-system extraction moves past the backup layer to access the directory structure of the device's data partition directly. On iOS, this is typically achieved by exploiting a known vulnerability or using a jailbreak to elevate privilege, then communicating through a privileged AFC service (AFC2) that exposes the full file system rather than only the media partition. Modern forensic tools from Cellebrite and MSAB include built-in jailbreak capabilities that apply a temporary privilege elevation without permanently modifying the device.
On Android devices, file-system extraction generally requires root access, either because the device ships with an unlocked bootloader (common on developer handsets and some Chinese market devices), because a rooting exploit is available for the specific firmware version, or because the device has been rooted by the owner. Once root access is obtained, the examiner can pull the full data partition using the adb pull command or a dedicated tool, retrieving every accessible file including those outside the backup scope.
The data returned by file-system extraction includes application databases that are excluded from backup, thumbnail caches, log files written by the system and apps, configuration plists and XML files, and temporary files in app containers that may contain fragments of user activity. Forensically significant finds often come from SQLite databases that applications use for local storage: messaging apps store their conversation history in SQLite, mapping apps write location history to SQLite, and browsers write history, cookies, and cache indices to SQLite databases that the backup API may not fully expose.
Scope and limitations: a structured comparison
Understanding what each method can and cannot return is the foundation of acquisition planning. The table below compares the two methods across the dimensions most relevant to a forensic investigation.
| Dimension | Logical acquisition | File-system extraction |
|---|---|---|
| Access layer | Vendor backup API | Mounted file system or privileged service |
| Device modification required | None | Temporary jailbreak or root may be needed |
| Contacts, calls, SMS | Yes | Yes (richer, includes app databases) |
| Application data (backup-excluded apps) | No | Yes |
| Deleted records | No (API surfaces only live data) | Partial (files in trash or unremoved app caches only) |
| Unallocated storage / file carving | No | No |
| Encryption obstacle | Backup password blocks content | Full-disk encryption (FBE) limits scope without key |
| Speed | Fast (minutes) | Moderate (tens of minutes to hours) |
| Works on locked device | Only with valid pairing record | Requires passcode or exploit |
| Admissibility risk | Low (vendor-sanctioned interface) | Medium (exploit use may require expert justification) |
The boundary between file-system extraction and physical acquisition is defined by unallocated space. Physical acquisition produces a sector-by-sector image of the storage chip, including every unallocated block where deleted file fragments may survive. File-system extraction operates at the file level: it retrieves files that exist in the directory structure but cannot see the space between them. For investigations where deleted message recovery or file carving is a priority, physical techniques are required. See Physical Acquisition Techniques and JTAG and Chip-Off Acquisition for those methods.
Tools and their approaches
Cellebrite UFED is the most widely deployed commercial mobile forensic platform. It supports logical, file-system, physical, and chip-off modes within a single interface. For logical extraction, UFED sends standard backup requests to iOS and Android devices and parses the results. For file-system extraction, it applies built-in exploit packages appropriate to the device model and firmware version, then mounts the file system to copy the data partition. UFED Physical Analyzer provides post-acquisition parsing and reporting.
MSAB XRY operates similarly, with a hardware kit that connects to the device and software that guides the examiner through acquisition mode selection. XRY offers logical and file-system modes and uses its own exploit library for privileged access. The company's XAMN software handles parsing and timeline analysis. Both Cellebrite and MSAB update their exploit libraries in response to new device models and firmware releases, which means a tool version that successfully performed file-system extraction on one firmware version may fail on the next.
Magnet AXIOM includes an acquisition module (Magnet ACQUIRE) that supports logical and file-system extraction, with AXIOM Process handling artefact parsing across mobile and computer evidence. Open-source options remain relevant, particularly for verification. The libimobiledevice library provides command-line access to the iOS backup protocol and AFC service, allowing examiners to reproduce a logical acquisition independently. For Android, the ADB toolchain is universal and can be scripted to pull specific directories or the full data partition when root is available.
Platform-specific considerations
iOS devices have become progressively more restrictive with each major release. The introduction of File-Based Encryption (FBE) in iOS 8, the move to the Secure Enclave processor, and Apple's consistent policy of patching the vulnerabilities exploited for file-system access have shortened the window in which a given exploit remains effective. As of iOS 17 and later, file-system extraction on devices without a known jailbreak requires either the passcode or, in some cases, a forensic-grade tool update that incorporates newly discovered vulnerabilities. Logical extraction through the backup API remains available provided a pairing record exists and the backup is not password-protected.
Android fragmentation works in both directions for the forensic examiner. The diversity of manufacturers and firmware versions means that a privilege escalation vulnerability affecting one device family may not exist on another. Devices from manufacturers that ship with relaxed security policies or unlocked bootloaders are more accessible. Google Pixel devices running recent Android versions with full-disk encryption and verified boot are among the harder targets for file-system extraction. Older Android versions (pre-7.0) with ADB backup enabled and no screen lock are among the easiest targets for logical acquisition.
SIM card data is not recovered through either logical or file-system acquisition methods applied to the handset. SIM data, including the ICCID, IMSI, stored contacts, and SMS records held on the card itself, requires dedicated SIM card reading hardware. See SIM Card Forensics for that workflow.
Legal framework and evidence integrity
Regardless of acquisition method, the fundamental requirements for evidential integrity are the same: documented authority, recorded chain of custody, and a cryptographic hash that can demonstrate the acquired data has not been altered. In the United States, a warrant is generally required for device searches following Riley v. California (2014), which held that mobile phones are not subject to the search-incident-to-arrest exception. In the United Kingdom, the Computer Misuse Act 1990, the Police and Criminal Evidence Act 1984, and the Investigatory Powers Act 2016 govern authority to access device data. In the European Union, the proposed e-Evidence Regulation and existing national laws apply. India's framework is now the Bharatiya Nagarik Suraksha Sanhita 2023 and the Digital Personal Data Protection Act 2023.
File-system extraction that relies on a security exploit raises an additional question in some jurisdictions: does applying an exploit to obtain access constitute unauthorised modification of the device, and does that affect the admissibility of the evidence obtained? Courts in the United States, United Kingdom, and Australia have generally accepted properly documented forensic tool use as lawful when conducted under valid authority, but the examiner must be able to explain in plain terms what the tool did, whether it wrote any data to the device, and whether it left residual changes. Tools that apply only temporary, non-persistent jailbreaks and do not alter user data partitions are in a stronger position than those that permanently modify the device.
Which type of data is returned by logical acquisition but NOT by file-system extraction?
Key Takeaways
- Logical acquisition uses vendor-provided backup APIs to retrieve a defined set of files and records; it is fast, non-destructive, and works on unmodified devices, but is limited to what the OS chooses to expose and cannot reach deleted data or unallocated storage.
- File-system extraction retrieves the full accessible directory tree by mounting the file system or using a privileged service layer, capturing application databases and cache files outside the backup scope, but still cannot access unallocated sectors where deleted data may reside.
- iOS backup encryption and Android application backup exclusion flags are the two most common API-level barriers encountered in logical acquisition; file-system extraction via temporary jailbreak is the standard workaround when passcode is known.
- Leading tools (Cellebrite UFED, MSAB XRY, Magnet AXIOM) support both acquisition modes within one platform, but exploit availability is firmware-specific and updates frequently; open-source tools such as libimobiledevice and adb provide independent verification paths.
- Legal authority, chain of custody documentation, and immediate SHA-256 hashing of acquired data are required regardless of acquisition method; jurisdictions including the United States (Riley v. California), the United Kingdom (PACE 1984), and India (BNSS 2023) all impose specific prerequisites before a device can be searched.
What is the difference between logical acquisition and file-system acquisition?
Can logical acquisition recover deleted data?
What tools are commonly used for logical and file-system acquisition?
Does logical acquisition work on locked devices?
How does acquisition method choice affect admissibility of mobile evidence?
Test yourself on Mobile and Network Forensics with free, timed mocks.
Practice Mobile and Network Forensics questionsSpotted an error in this page? Report a correction or read our editorial standards.