WEBVTT

00:00:01.632 --> 00:00:04.369 align:middle line:84%
For USB debugging-- this
is essentially that wall

00:00:04.369 --> 00:00:05.202 align:middle line:90%
that I talked about.

00:00:05.202 --> 00:00:07.302 align:middle line:84%
The little green guy
walks across the bridge.

00:00:07.302 --> 00:00:09.842 align:middle line:90%
He could hit this wall.

00:00:09.842 --> 00:00:12.602 align:middle line:84%
In order to enable it, you
have to go into the Settings,

00:00:12.602 --> 00:00:14.900 align:middle line:84%
and you have to tap the
Build Number seven times.

00:00:14.900 --> 00:00:16.442 align:middle line:84%
Now, as you're
tapping it, it's going

00:00:16.442 --> 00:00:19.442 align:middle line:84%
to say developer mode
is soon to be enabled,

00:00:19.442 --> 00:00:21.122 align:middle line:84%
and then it'll say
developer mode.

00:00:21.122 --> 00:00:23.252 align:middle line:84%
You then go into Developer
Mode, and you check

00:00:23.252 --> 00:00:26.502 align:middle line:90%
the box for USB Debugging.

00:00:26.502 --> 00:00:29.202 align:middle line:84%
I'm going to show you some
tips and hurdles that you

00:00:29.202 --> 00:00:32.892 align:middle line:84%
may hit in section 2 during
the acquisition section on ways

00:00:32.892 --> 00:00:35.682 align:middle line:84%
to overcome any issues
that you could have.

00:00:35.682 --> 00:00:38.442 align:middle line:84%
Something to remember is,
if there is mobile device

00:00:38.442 --> 00:00:41.502 align:middle line:84%
management on that Android,
USB debugging could

00:00:41.502 --> 00:00:43.452 align:middle line:90%
be blocked by an administrator.

00:00:43.452 --> 00:00:45.467 align:middle line:84%
If that is the
case, the only way

00:00:45.467 --> 00:00:46.842 align:middle line:84%
you're going to
acquire this data

00:00:46.842 --> 00:00:50.214 align:middle line:84%
is going to be through
Bluetooth or manual examination.

00:00:50.214 --> 00:00:52.422 align:middle line:84%
Or you could always try to
extract cloud information.
