Skip to content

iOS Acquisition: Backups, Full File System and sysdiagnose

How to acquire an iPhone: device state, encrypted versus unencrypted backups, full file system extraction, sysdiagnose and iCloud, and what each reaches.

Published on 12 min read

Acquiring an iPhone is not one operation but a choice between levels, each reaching a different slice of the evidence. A local backup is easy and well understood, but by design it leaves out most of what makes iOS forensics valuable: pattern-of-life databases, location history, caches and SQLite write-ahead logs. A full file system extraction reaches almost everything, but depends on the device model, the iOS version, the device state and specialised tools. A sysdiagnose captures logs and system state that neither of them keeps for long. And iCloud may hold data the device no longer has.

This guide walks through those levels in the order you will meet them in a real case: what to do before touching the device, how backups work and how to make the most of them, what a full file system extraction adds and what it requires, when to collect a sysdiagnose, and how to document the result so it survives scrutiny. It stays at the level of lawful collection: no passcode bypass recipes, no exploit instructions.

Before you touch the device

Most acquisition failures happen in the first hour, long before any tool is connected. The priorities are legal authority, preserving the device's state, and stopping remote changes.

Authority first. Confirm what your warrant, consent or corporate mandate covers: the device, its backups on computers, cloud accounts, or all three. iCloud data is a separate target with its own legal route.

Record the state you found. Photograph the screen, note whether it is on, locked or unlocked, the time shown against a reference clock, battery level, and visible notifications. Note the model if it is visible, and never guess the passcode: failed attempts can escalate delays and, if the owner enabled it, erase the device after ten tries.

Keep it powered. An iPhone that has been unlocked since boot is in AFU state: the keys protecting most app data are in memory. If it powers off, restarts or runs out of battery, it returns to BFU and much of the data becomes unreadable until the passcode is entered. Connect a power bank during transport. Be aware that from iOS 18.1 a device that stays locked for an extended period (reported as 72 hours) restarts on its own: time matters.

Isolate it from networks. A connected device keeps receiving messages, syncing with iCloud and can be erased remotely through Find My. A Faraday bag or enclosure (with power inside) is the common answer. Enabling Airplane Mode from Control Center is an alternative on an unlocked device, but it is an interaction with the device that you must record, and it may not disable Wi-Fi or Bluetooth depending on the user's settings.

Mind USB Restricted Mode. Since iOS 11.4.1, when a locked device has not been unlocked or connected to a trusted accessory for about an hour, its port stops accepting data connections until it is unlocked. Lockdown Mode, introduced with iOS 16, tightens this further. Plan the order of operations with this clock in mind.

The acquisition levels at a glance

LevelReachesRequiresTypical tools
Media via AFCPhotos and videos in DCIMUnlocked, trusted deviceifuse, Finder / Photos import
Unencrypted backupMessages, contacts, photos, notes, many app containersUnlocked, trusted deviceidevicebackup2, pymobiledevice3, iMazing, UFADE
Encrypted backupEverything above plus call history, website history, saved passwords, Wi-Fi settings, HealthSame, plus a known backup passwordSame tools
sysdiagnoseUnified logs, shutdown.log, process and network state, crash reportsPhysical access to the buttons, unlocked for retrievalDevice buttons, pymobiledevice3, MVT for analysis
Full file systemApp containers, system databases, caches, WAL files, keychain (depending on method)Supported model and iOS version, often AFUCellebrite, Magnet AXIOM, Elcomsoft iOS Forensic Toolkit
iCloudBackups and synced data held by AppleLegal process or lawful credentials; limited by Advanced Data ProtectionProvider response, commercial cloud tools

The artifact pages on this site each state the minimum level in their Acquisition field.

Logical acquisition: iTunes and Finder backups

A backup is produced by the device itself through the mobilebackup2 service, over the same lockdown protocol that Finder, iTunes and the Apple Devices app use. The examiner's tool asks, the device decides what to include.

Pairing and trust

Before any backup, the device must trust the computer. On a new computer the device shows a Trust This Computer? prompt, and since iOS 11 the user must also enter the passcode. The result is a pairing record stored on both sides.

This has two consequences. First, you need the device unlocked and the passcode to create a new pairing. Second, the owner's own computers hold pairing records (/private/var/db/lockdown/ on macOS, %ProgramData%\Apple\Lockdown\ on Windows) and possibly older backups. Seizing and examining those computers can be as valuable as the phone itself.

Unencrypted versus encrypted backups

Apple's documentation is explicit: an encrypted backup can include data an unencrypted one does not, namely saved passwords, Wi-Fi settings, website history, Health data and call history. In artifact terms, that means CallHistory.storedata and Safari's History.db will usually be missing from an unencrypted backup, while sms.db, AddressBook and Photos.sqlite are present in both.

The recommended practice is therefore to take an encrypted backup with a password you set. With libimobiledevice:

idevice_id -l                                   # confirm the device UDID
ideviceinfo -k ProductVersion                   # record the iOS version
idevicebackup2 encryption on '<case-password>'   # set your own backup password
idevicebackup2 backup --full ./case/backup/
shasum -a 256 -b ./case/backup/*/Manifest.* > ./case/backup.sha256

The equivalent with pymobiledevice3 is pymobiledevice3 backup2 encryption on followed by pymobiledevice3 backup2 backup --full. GUI tools such as iMazing and the open-source UFADE wrap the same service with case documentation features. Enabling encryption changes a device setting, which persists after you disconnect: record it.

Decrypt for analysis with the password you set, using mvt-ios decrypt-backup, iphone_backup_decrypt or your forensic suite, and work only on the decrypted copy. The structure you will find is described on the Manifest.db and Manifest.plist page.

Existing backups on computers

Backups already on the owner's computers are evidence in their own right. They may predate deletions on the phone, and archived backups survive the next backup. Copy the whole MobileSync/Backup folder with timestamps, check each Info.plist for the device name and last backup date, and look for older copies in Time Machine, file system snapshots and cloud-synced folders.

When the backup password is unknown

If the owner already set a backup password, every new backup is encrypted with it and you cannot change it without knowing it. The lawful options are, in order of preference: obtain the password through your legal process; attempt recovery on an existing backup with an authorised password attack (Hash Extractor turns Manifest.plist into a hashcat or John hash in the browser, but recent backups use a very high key-derivation iteration count, so only weak passwords fall); or reset the backup password on the device through Reset All Settings, which requires the device passcode and also resets network, keyboard and other settings. The last option alters the device, so it needs explicit approval and careful documentation.

What a backup never contains

Even encrypted, a backup excludes caches, most system databases and anything an app marks as not to be backed up. KnowledgeC and Biome, Significant Locations, many third-party app databases and the write-ahead logs that hold recent SQLite changes are all absent. That gap is what a full file system extraction fills.

Full file system extraction

A full file system extraction copies the files of the data partition as the operating system sees them: /private/var/mobile, every app container, system databases, logs and caches. For modern iPhones it is the highest level of acquisition available, because hardware encryption makes a chip-level physical image useless without the device's keys.

What it adds

  • Pattern-of-life and location databases, with their WAL files.
  • Complete third-party app containers, including those excluded from backups.
  • SQLite freelist pages and journals, where deleted records survive.
  • System logs and state that a sysdiagnose only partly captures.
  • Depending on the method, a decrypted keychain, which in turn can unlock app-level encryption.

How it is obtained

Reading those files requires code running on the device with elevated privileges. In practice this comes from commercial forensic vendors, through agent-based extractions or through exploits for specific models and iOS versions. On older hardware (A11 and earlier, up to the iPhone 8 and iPhone X), a publicly known bootrom vulnerability enables extractions that do not depend on the iOS version, although newer iOS releases limit what can be reached when a passcode is set.

This guide does not describe those techniques. What matters for the examiner is to verify, before relying on a tool, that it supports the exact model and iOS build, to understand whether the extraction modifies the device (installing an agent does), and to keep the vendor's logs as part of the record.

BFU, AFU and data protection

Every file on iOS belongs to a data protection class. Class C, the default for most app data, is readable once the device has been unlocked after boot. A BFU device therefore yields very little even with the best tools: some system files, class D data, and not much else. An AFU device, even locked, exposes most databases. This is the single strongest reason for the handling rules at the start of this guide.

sysdiagnose

A sysdiagnose is a diagnostic archive the device generates on request. It needs no agent, no exploit and no pairing to create, which makes it a low-impact complement to any other acquisition.

Triggering and retrieving

On an iPhone, press and briefly hold both volume buttons and the side button together until the device vibrates. Generation runs in the background for several minutes. The resulting sysdiagnose_...tar.gz appears under Settings, Privacy & Security, Analytics & Improvements, Analytics Data. From there it can be shared, or pulled from a trusted computer with crash report tools such as pymobiledevice3. Its crash sysdiagnose command waits for and collects a new archive, but generating one still requires interaction on the device (the button combination), so it is not a fully remote trigger. Note the exact time you pressed the buttons: it shows up in the archive and anchors your own actions in the timeline.

What is inside

  • system_logs.logarchive: the device's Unified Logs, readable on a Mac with log show --archive. Retention is short, typically days, so every hour of delay costs evidence.
  • shutdown.log: processes still running at each reboot, a known source of spyware indicators.
  • Process lists, network interface state, Wi-Fi and Bluetooth information, mobile activation and accounts data, crash and spin reports.

Analysis tools include the EC-DIGIT-CSIRC sysdiagnose analyser and, for compromise checks against published indicators, MVT. In suspected spyware cases, collect a sysdiagnose first, then an encrypted backup for MVT's check-backup, then a full file system if available.

Other sources

iCloud. Apple can hold device backups, Messages in iCloud, Photos, Safari data and more. Access is through legal process to Apple or through lawful use of the account's credentials with a commercial cloud tool. With Advanced Data Protection (available from iOS 16.2), most categories are end-to-end encrypted and Apple cannot provide their content. Messages and Photos synced to iCloud can also mean that the phone holds only a partial local copy.

Media over AFC. On an unlocked, trusted device, the Apple File Conduit service exposes DCIM without a backup. It is quick for triage but gives you files without the Photos.sqlite context.

Companion devices. A Mac or iPad on the same Apple Account can hold the same messages, synced browsing history and FaceTime calls. They are often easier to acquire than the phone.

Verification and documentation

A defensible acquisition is one somebody else could reproduce and check. For every step, record:

  • Date and time (with the time source), who performed it, and the device state before and after.
  • Device identifiers: model, serial, UDID, IMEI where applicable, iOS version and build.
  • Tool names and versions, commands or options used, and any change made to the device (backup encryption enabled, agent installed, settings reset).
  • Hashes of every resulting archive or folder, computed immediately and verified before analysis.

Then check coverage: list the domains in Manifest.db, confirm the presence of the databases your case depends on, and note explicitly what the chosen level could not reach. A report that says "Significant Locations were not examined because the acquisition was a backup" is stronger than one that silently omits them.

A practical decision order

  1. Secure authority, power and network isolation. Record the state.
  2. If the device is unlocked or you have the passcode, take a sysdiagnose and an encrypted backup with your own password.
  3. If the case needs pattern of life, location, deleted records or third-party app data, pursue a full file system extraction with a tool that supports the model and iOS version, while the device is still AFU.
  4. Collect the owner's computers for existing backups and pairing records, and request iCloud data through the proper channel.
  5. Verify hashes, document coverage and start the analysis from copies.

Common mistakes

  • Letting the device restart or run out of power, turning AFU into BFU.
  • Taking an unencrypted backup and concluding the user made no calls or never browsed.
  • Opening SQLite databases in place, which merges the WAL and destroys recoverable records.
  • Forgetting existing backups on the owner's computers.
  • Reporting what the tool showed without saying what the acquisition level could not reach.

Once you have the data, the artifact pages take over: start with sms.db, the backup structure and KnowledgeC and Biome, and use Mac Absolute Time conversions to put every source on the same UTC clock.

Related guides

05 · Location & Movement

iOS Location Forensics: Where Was the iPhone?

Every iPhone location source compared: Significant Locations, photo GPS, Wi-Fi networks, locationd caches, Biome and app data, with precision and retention.

Read guide