WEBVTT

00:00:01.815 --> 00:00:04.065 align:middle line:84%
In this course, we
used to break down

00:00:04.065 --> 00:00:06.825 align:middle line:84%
all of these differences here
and teach you how to do it.

00:00:06.825 --> 00:00:10.705 align:middle line:84%
Sadly, some of them are kind
of a trend that are going away.

00:00:10.705 --> 00:00:13.905 align:middle line:84%
So if we look at the bottom,
JTAG, ISP, and Chip-off.

00:00:13.905 --> 00:00:16.125 align:middle line:84%
This is a "use it
or lose it" skill.

00:00:16.125 --> 00:00:18.075 align:middle line:84%
I took my training
from Teel Tech,

00:00:18.075 --> 00:00:20.485 align:middle line:84%
and Bob Elder taught
me amazing things.

00:00:20.485 --> 00:00:24.075 align:middle line:84%
However, it is literally
use it or lose it.

00:00:24.075 --> 00:00:24.885 align:middle line:90%
Keep that in mind.

00:00:24.885 --> 00:00:26.875 align:middle line:84%
If it's not something
you're doing every day,

00:00:26.875 --> 00:00:28.125 align:middle line:90%
it's not going to be relevant.

00:00:28.125 --> 00:00:31.215 align:middle line:84%
Also, there are a lot of phones
where this does not pertain

00:00:31.215 --> 00:00:33.225 align:middle line:90%
anymore because of encryption.

00:00:33.225 --> 00:00:36.885 align:middle line:84%
If it's file-based
encryption on that device,

00:00:36.885 --> 00:00:40.915 align:middle line:84%
the decryption must happen
on the device or not at all.

00:00:40.915 --> 00:00:43.485 align:middle line:84%
But let's talk through
some of these other ones.

00:00:43.485 --> 00:00:45.285 align:middle line:90%
Bootloader extractions.

00:00:45.285 --> 00:00:49.855 align:middle line:84%
These may also not be available
on newer Android devices.

00:00:49.855 --> 00:00:51.445 align:middle line:90%
So keep that in mind.

00:00:51.445 --> 00:00:54.165 align:middle line:84%
But if you enter your make and
model into your forensic tool

00:00:54.165 --> 00:00:56.835 align:middle line:84%
of choice and it says, hey, I
can do a bootloader extraction,

00:00:56.835 --> 00:00:59.145 align:middle line:84%
what this means is
a custom bootloader

00:00:59.145 --> 00:01:02.415 align:middle line:84%
is going to be injected into
RAM or the memory of that device

00:01:02.415 --> 00:01:03.775 align:middle line:90%
before it boots.

00:01:03.775 --> 00:01:07.305 align:middle line:84%
And it lets you get,
usually, physical acquisition

00:01:07.305 --> 00:01:09.415 align:middle line:90%
support for it.

00:01:09.415 --> 00:01:11.425 align:middle line:90%
Custom recovery images.

00:01:11.425 --> 00:01:14.095 align:middle line:84%
This one is only supported
on Android devices that

00:01:14.095 --> 00:01:16.465 align:middle line:90%
are older and not encrypted.

00:01:16.465 --> 00:01:18.335 align:middle line:84%
That's rare, if
you think about it.

00:01:18.335 --> 00:01:21.085 align:middle line:84%
Most Androids do
have either full disk

00:01:21.085 --> 00:01:23.095 align:middle line:84%
encryption or
file-based encryption

00:01:23.095 --> 00:01:24.775 align:middle line:90%
enabled on that handset.

00:01:24.775 --> 00:01:28.705 align:middle line:84%
But if you come across an
older one, you can try this.

00:01:28.705 --> 00:01:32.035 align:middle line:84%
If you read the
notes of this page,

00:01:32.035 --> 00:01:34.525 align:middle line:84%
AXIOM's really good
at recovery images,

00:01:34.525 --> 00:01:38.095 align:middle line:84%
on letting you download and
install your own on the device.

00:01:38.095 --> 00:01:41.285 align:middle line:90%
Just be careful with it.

00:01:41.285 --> 00:01:43.295 align:middle line:90%
Emergency download mode.

00:01:43.295 --> 00:01:45.065 align:middle line:84%
This is a way that
you could do it

00:01:45.065 --> 00:01:48.415 align:middle line:84%
through keystrokes on the
device or with specialized cable

00:01:48.415 --> 00:01:53.215 align:middle line:84%
to put the device in a low-level
access mode that provides

00:01:53.215 --> 00:01:58.435 align:middle line:84%
direct access to that chipset to
get a more physical acquisition

00:01:58.435 --> 00:01:59.605 align:middle line:90%
of that device.

00:01:59.605 --> 00:02:03.895 align:middle line:84%
There is a group on day
five, MDFA, the Mobile Device

00:02:03.895 --> 00:02:06.415 align:middle line:84%
Forensic Analysis Group,
that you can join.

00:02:06.415 --> 00:02:10.315 align:middle line:84%
There is amazing information
put out there by Scott

00:02:10.315 --> 00:02:14.095 align:middle line:84%
on how to get devices into EDL
mode and what is supported.

00:02:14.095 --> 00:02:18.895 align:middle line:84%
Now, EDL mode should not be
disruptive to the device.

00:02:18.895 --> 00:02:20.695 align:middle line:90%
Bootloader extractions can be.

00:02:20.695 --> 00:02:23.155 align:middle line:84%
And the reason I'm mentioning
this custom recovery images

00:02:23.155 --> 00:02:24.235 align:middle line:90%
and bootloader--

00:02:24.235 --> 00:02:27.205 align:middle line:84%
if you try to push
something to a device that's

00:02:27.205 --> 00:02:30.583 align:middle line:84%
not the correct model, you could
brick or ruin that evidence.

00:02:30.583 --> 00:02:31.375 align:middle line:90%
So be very careful.

00:02:31.375 --> 00:02:33.865 align:middle line:84%
Make sure you're
doing device-specific

00:02:33.865 --> 00:02:37.615 align:middle line:84%
and know that these are
additional extraction methods.

00:02:37.615 --> 00:02:41.065 align:middle line:84%
These should kind of
be used toward the end,

00:02:41.065 --> 00:02:42.935 align:middle line:84%
like, you've exhausted
all other options.

00:02:42.935 --> 00:02:46.645 align:middle line:84%
So for bootloader,
custom recovery, and EDL,

00:02:46.645 --> 00:02:49.015 align:middle line:84%
you've tried other
extraction methods.

00:02:49.015 --> 00:02:51.385 align:middle line:84%
For JTAG, ISP, Chip-off--
that's typically

00:02:51.385 --> 00:02:52.945 align:middle line:90%
your last step anyway.

00:02:52.945 --> 00:02:55.525 align:middle line:84%
But then we have these
three in between.

00:02:55.525 --> 00:02:57.838 align:middle line:84%
And these are going
to be unique to UFED

00:02:57.838 --> 00:02:59.005 align:middle line:90%
at the time of writing this.

00:02:59.005 --> 00:03:01.645 align:middle line:90%
So Qualcomm Live, Huawei--

00:03:01.645 --> 00:03:03.295 align:middle line:84%
which is going to be
called Kirin live,

00:03:03.295 --> 00:03:04.915 align:middle line:90%
I believe-- and MTK Live.

00:03:04.915 --> 00:03:08.215 align:middle line:84%
Depending on the chip that's
on that device, what it does is

00:03:08.215 --> 00:03:10.705 align:middle line:84%
it puts it into
a state where you

00:03:10.705 --> 00:03:14.395 align:middle line:84%
may be able to get a full
file system acquisition

00:03:14.395 --> 00:03:16.675 align:middle line:90%
of modern Android devices.

00:03:16.675 --> 00:03:17.905 align:middle line:90%
It's awesome.

00:03:17.905 --> 00:03:21.145 align:middle line:84%
So if it can work, make
sure you're leveraging that.

00:03:21.145 --> 00:03:23.425 align:middle line:84%
In Section 2, I will
talk you through using

00:03:23.425 --> 00:03:26.185 align:middle line:84%
some of the Qualcomm Live,
Kirin Live, and MTK--

00:03:26.185 --> 00:03:26.755 align:middle line:90%
Live methods.
