I started filling in the gaps to missing APOLLO modules. While doing this I realized there was some capability that was missing with the current script that had to be updated. As far as script updates go the following was done:

Support for multiple database name -Depending on the iOS version being used the database names may be different but the SQL query itself is the same. Instead of creating many redundant modules I now have it looking for the different database filenames.
Support for multiple queries on different iOS versions- You will now notice that all the modules have been updated with iOS version indicators and multiple SQL queries compatible for that version. Some going back as far as iOS 8! I put in as much legacy support as I had data for. I will likely not add much more unless it is by special request. I can’t imagine there is a whole lot of iOS 8 analysis going on out there, but you never know! I have kept it to major iOS release numbers and have tested with the data I have but it may have changed with a minor point release, if you find this to be true please feel free to let me know!
Module Timestamp Rearrangement and Module Cleanup– I’ve started to go through some of the modules and move the items around to make it easier to see what is going on with each record. I’ve mostly just moved the timestamps toward the end since most of them are shown in the Key column. I’ve also removed some superfluous columns and extraneous junk in the queries. I’m really only trying to extract the most relevant data.

A few notes on script usage change. The script flags have changed, with the added arguments of -p = platform (iOS support only for now), and -v = iOS Version. You may also notice the new ‘yolo’ option – this one will likely be error prone if you are not careful. Use this when you what to run it on any database from any platform. It can also be used with your own custom modules if you don’t have versioning in them.

An example of the module changes is below. Notice the multiple databases listed. In this example, the same location data can be extracted from the cache_encryptedB.db or the cache_encrypted A.db databases depending on the iOS versions. The version information is listed in the “VERSIONS” key, while the specific queries have versions listed in the [SQL Query …] brackets, this is the version that the apollo.py script is following.

The big updates were with the modules, lots of new support! I now have support for 129 different pattern-of-life items! Most of the support is for iOS, however if you run the queries themselves on similar macOS databases you will find that many of them will work. Better macOS support is coming, I promise.

Application Specific Usage:

Chat – SMS, iMessage, & FaceTime messages extracted from the sms.db database.
- sms_chat

Call History – Extracted from CallHistory.storedata database.
- call_history

Safari Browsing – Extracted from the History.db database.
- safari_history

Apple Pay/Wallet - Extracted from iOS passes23.sqlite database.
- Apple Pay Transactions - passes23_wallet_transactions
- Wallet Passes - passes23_wallet_passes

Location :

locationd - The following modules extract location data from the [lock]cache_encryptedA.db & cache_encryptedB.db databases. This will include various cellular and Wi-Fi based location tables as listed in the module filename.
- locationd_cacheencryptedAB_appharvest
- locationd_cacheencryptedAB_cdmacelllocation
- locationd_cacheencryptedAB_celllocation
- locationd_cacheencryptedAB_celllocationharvest
- locationd_cacheencryptedAB_celllocationlocal
- locationd_cacheencryptedAB_cmdacelllocationharvest
- locationd_cacheencryptedAB_indoorlocationharvest
- locationd_cacheencryptedAB_locationharvest
- locationd_cacheencryptedAB_ltecelllocation
- locationd_cacheencryptedAB_ltecelllocationharvest
- locationd_cacheencryptedAB_ltecelllocationlocal
- locationd_cacheencryptedAB_passharvest
- locationd_cacheencryptedAB_poiharvestlocation
- locationd_cacheencryptedAB_pressurelocationharvest
- locationd_cacheencryptedAB_scdmacelllocation
- locationd_cacheencryptedAB_wifilocation
- locationd_cacheencryptedAB_wifilocationharvest
- locationd_cacheencryptedAB_wtwlocationharvest
locationd – These modules extract motion data from the cache_encryptedC.db database. Not specific location data but will show device movement.
- locationd_cacheencryptedC_motionstatehistory
- locationd_cacheencryptedC_nataliehistory
- locationd_cacheencryptedC_stepcounthistory
routined – Extracts location data from the cache_encryptedB.db database. If you have a keen eye you will notice the database name is the same as from ‘locationd’. Completely different database with different data stored in two different directories.
- routined_cacheencryptedB_hint
- routined_cacheencryptedB_location

Health Workouts – Using the healthdb_secure.sqlite database I’ve extracted much of the metadata from workouts. I’ve also determined some of the workout types (ie: HIIT, Rower, Run, Walk, etc), but have not enumerated all of them yet. Please let me know if you come across others – easier if you do this on your own data and can easily look it up. Same for weather conditions (Sunny, Rainy, etc.).