WEBVTT

00:00:01.894 --> 00:00:04.864 align:middle line:84%
Commercial support for
creating backup files exist.

00:00:04.864 --> 00:00:07.924 align:middle line:84%
So there are two different
things that you may see.

00:00:07.924 --> 00:00:10.594 align:middle line:84%
At the top, we have the
File System extraction.

00:00:10.594 --> 00:00:12.364 align:middle line:90%
This was created with UFED.

00:00:12.364 --> 00:00:16.324 align:middle line:84%
And do you see how it has
backup0, backup1, 2, 3, and so

00:00:16.324 --> 00:00:17.024 align:middle line:90%
on?

00:00:17.024 --> 00:00:19.954 align:middle line:84%
That's how many times I had to
press Backup My Data, Backup My

00:00:19.954 --> 00:00:22.024 align:middle line:90%
Data.

00:00:22.024 --> 00:00:24.904 align:middle line:84%
Then we could see here we have
Google Android Backup ADB.

00:00:24.904 --> 00:00:28.174 align:middle line:84%
We can see I loaded a
backup.ab, and we have all

00:00:28.174 --> 00:00:30.404 align:middle line:90%
of the data files listed here.

00:00:30.404 --> 00:00:34.574 align:middle line:84%
Now, what gets frustrating,
the default for Android

00:00:34.574 --> 00:00:38.832 align:middle line:84%
is to not include user databases
for applications in the backup.

00:00:38.832 --> 00:00:40.874 align:middle line:84%
So even though you look
at this, and you're like,

00:00:40.874 --> 00:00:43.814 align:middle line:90%
oh, it's got 71 files.

00:00:43.814 --> 00:00:45.194 align:middle line:90%
It has this many files.

00:00:45.194 --> 00:00:47.234 align:middle line:84%
You may find that the
user database that you're

00:00:47.234 --> 00:00:49.894 align:middle line:90%
hoping to see is missing.

00:00:49.894 --> 00:00:55.454 align:middle line:84%
We are going to need to get
full file system access to gain

00:00:55.454 --> 00:00:57.584 align:middle line:90%
rights to look at those files.

00:00:57.584 --> 00:00:59.084 align:middle line:84%
Something else
you're going to see

00:00:59.084 --> 00:01:03.104 align:middle line:84%
is the file paths may not
make sense, depending the type

00:01:03.104 --> 00:01:04.704 align:middle line:90%
of extraction that you have.

00:01:04.704 --> 00:01:08.864 align:middle line:84%
So what I recommend is that,
instead of looking at data,

00:01:08.864 --> 00:01:14.744 align:middle line:84%
data, com, Android, providers,
telephony, sms, mms DB,

00:01:14.744 --> 00:01:16.694 align:middle line:90%
look for mmssms.db.

00:01:16.694 --> 00:01:18.764 align:middle line:84%
Just search for
the database name.

00:01:18.764 --> 00:01:19.634 align:middle line:90%
Simplify it.

00:01:19.634 --> 00:01:23.084 align:middle line:84%
Don't dig so deep that you
can't find the full paths.

00:01:23.084 --> 00:01:25.454 align:middle line:90%
The paths may not match.

00:01:25.454 --> 00:01:29.384 align:middle line:84%
The database will match
if and only if it exists.

00:01:29.384 --> 00:01:30.734 align:middle line:90%
So use your cheat sheet.

00:01:30.734 --> 00:01:31.694 align:middle line:90%
Get ready to dig.

00:01:31.694 --> 00:01:32.834 align:middle line:90%
Do not be intimidated.

00:01:32.834 --> 00:01:34.634 align:middle line:90%
Keyword search.

00:01:34.634 --> 00:01:38.414 align:middle line:84%
Look for anything you can to
get a glimpse of what you see.

00:01:38.414 --> 00:01:41.234 align:middle line:84%
Backups of Android may
be extremely restricted.

00:01:41.234 --> 00:01:42.344 align:middle line:90%
That's the bottom line.
