WEBVTT

00:00:05.359 --> 00:00:11.840
accidents happen and the team at drive savers deals with

00:00:09.200 --> 00:00:16.400
the fallout of a lot of accidents so they sponsored this video to tour their

00:00:14.000 --> 00:00:20.560
sick facility in california to show the process of recovering the data from

00:00:18.320 --> 00:00:24.480
mobile devices like iphones that have gone through everything from being

00:00:22.560 --> 00:00:28.560
dropped out of a moving car to being thrashed by a gorilla at the zoo to

00:00:26.400 --> 00:00:32.960
being literally destroyed in a plane crash this tour is gonna be a little

00:00:30.880 --> 00:00:37.840
different though because i'm actually in my studio at home due to travel

00:00:34.800 --> 00:00:40.840
restrictions but it'll still be really

00:00:37.840 --> 00:00:40.840
cool

00:00:47.600 --> 00:00:53.840
every phone recovery starts with educating the customer drive savers data

00:00:52.000 --> 00:00:58.000
recovery my name is dylan how can i help you now the average person might think

00:00:56.000 --> 00:01:03.280
that data recovery is similar to what the apple store might do but in reality

00:01:00.480 --> 00:01:07.920
it is very unusual for data recovery to be covered by any sort of manufacturer

00:01:05.439 --> 00:01:13.040
warranty and the process is totally different when you send a device in for

00:01:10.560 --> 00:01:17.040
repair it's much more economical for a company like apple to simply replace

00:01:15.040 --> 00:01:20.799
whatever is broken rather than spending long hours diagnosing and fixing board

00:01:19.520 --> 00:01:26.000
level faults now this would be fine except that they

00:01:23.520 --> 00:01:31.600
see components like the main board as one piece so if there's an issue with it

00:01:28.880 --> 00:01:36.960
or anything that's attached to it it's gone that means no data they operate

00:01:34.880 --> 00:01:41.119
this way because a manufacturer is only concerned with preventing devices from

00:01:38.799 --> 00:01:45.600
breaking it's uneconomical to try to fix them once they do which is why the most

00:01:43.360 --> 00:01:50.640
straightforward data recovery operations are often though not always the ones

00:01:48.000 --> 00:01:54.880
where the issue is logical rather than physical and no hardware actually needs

00:01:53.040 --> 00:01:59.119
to be changed and in order to make this process as smooth as possible drive

00:01:57.200 --> 00:02:03.040
savers has actually developed their own in-house tools to take out some of the

00:02:01.439 --> 00:02:08.160
guesswork something that they're now also using for t2 mac recovery so when a

00:02:05.840 --> 00:02:13.440
device arrives drive saver's first step is to give it a once over if it's boot

00:02:10.399 --> 00:02:15.440
looping in recovery mode or it powers on

00:02:13.440 --> 00:02:18.480
but won't actually boot up there's a good chance that they can connect it

00:02:16.879 --> 00:02:21.440
with a lightning cable and perform the recovery that way

00:02:19.920 --> 00:02:24.879
very convenient but also dangerous

00:02:23.040 --> 00:02:29.760
one of the most important parts of this discovery process is checking the

00:02:26.959 --> 00:02:32.959
voltage and amperage of the device certain readings might point to a

00:02:31.360 --> 00:02:37.519
particular chip that's failed which could result in a data loss if a logical

00:02:35.519 --> 00:02:42.640
recovery is attempted directly it all comes down to experience 0.8 amps or

00:02:40.239 --> 00:02:46.480
higher is typical but other readings can be a strong indicator that it's a

00:02:44.480 --> 00:02:50.000
physical issue and it's time to crack the casing open

00:02:47.920 --> 00:02:54.160
at this stage it's best to start by looking for simple problems like shorts

00:02:52.000 --> 00:02:58.080
on the motherboard this can be done by freezing the logic board with a cold

00:02:55.840 --> 00:03:02.319
spray and looking for areas that thaw too quickly indicating excess heat or

00:03:01.200 --> 00:03:05.760
thanks to the wonders of modern technology it can also be done with a

00:03:04.319 --> 00:03:10.879
thermal camera using this method even very small shorts

00:03:08.560 --> 00:03:15.519
can be identified although finding the source of the short can be an entirely

00:03:13.120 --> 00:03:20.720
separate issue some simple shorts are fixable failed resistors can be replaced

00:03:18.319 --> 00:03:24.480
and burnt traces can in some cases be repaired as long as the technician

00:03:22.959 --> 00:03:28.720
doesn't drink too much coffee ahead of time i actually asked drive savers what

00:03:26.640 --> 00:03:33.519
their most important tool is and i was surprised to hear them say

00:03:30.840 --> 00:03:36.959
really while the particular model comes down to personal preference

00:03:35.440 --> 00:03:41.599
everyone there agrees that it is absolutely essential that the ends line

00:03:39.040 --> 00:03:46.239
up really well otherwise you might be transferring a component to a board only

00:03:43.599 --> 00:03:49.599
to have it go flying out and good luck holding on to something like a micro

00:03:47.840 --> 00:03:54.080
jumper if the ends don't match up absolutely perfectly those puppies are

00:03:52.239 --> 00:03:58.319
thinner than a human hair and even the breeze from someone walking past can

00:03:55.920 --> 00:04:02.720
blow them away never to be seen again other times the shorts are more complex

00:04:00.560 --> 00:04:07.120
or harder to get at if there's liquid damage you might remove the short only

00:04:04.720 --> 00:04:12.319
to find another one then corrosion under the chips and so on and so forth the

00:04:09.840 --> 00:04:16.959
worst is apparently milk now with any corrosion you start with a toothbrush if

00:04:15.040 --> 00:04:21.040
there's gunk under a chip you remove that chip and replace it if the board is

00:04:19.280 --> 00:04:25.040
completely corroded you need to use an ultrasonic cleaner not necessarily a

00:04:23.199 --> 00:04:29.360
super strong one you just want to get off as much of the gunk as you can so

00:04:26.960 --> 00:04:33.199
that you can start to look for shorts sometimes they're so bad though that

00:04:31.440 --> 00:04:37.680
when you start with a soft toothbrush you will literally have components just

00:04:35.280 --> 00:04:42.800
crumbling off the board and in cases like that you might end up doing a full

00:04:40.720 --> 00:04:48.320
chip swap where you are basically rebuilding the phone onto a donor device

00:04:46.240 --> 00:04:53.600
drive savers tries to source individual parts whether new or used but sometimes

00:04:51.199 --> 00:04:58.560
there's no other choice but to sacrifice a brand new device i mean look hey we

00:04:56.320 --> 00:05:02.320
told you data recovery ain't cheap right unfortunately

00:05:00.000 --> 00:05:07.919
yes it gets even worse aside from being a time consuming and risky operation on

00:05:05.120 --> 00:05:12.160
components that are ridiculously fragile this chip swap method also has some

00:05:10.400 --> 00:05:15.120
major limitations unless they could break apple's

00:05:13.520 --> 00:05:19.600
encryption which drive savers wouldn't do even if they could every component

00:05:17.280 --> 00:05:24.880
with apple's security measures baked in needs to be restored to at least a basic

00:05:22.160 --> 00:05:29.120
level of functionality the nand flash is what actually holds the data in an

00:05:26.479 --> 00:05:32.720
iphone so obviously we need that then there's the logic eprom which holds the

00:05:31.120 --> 00:05:37.039
firmware of the device that thing is super small about the size

00:05:35.039 --> 00:05:40.080
of a large grain of salt and if it disappears your data recovery effort is

00:05:39.120 --> 00:05:45.680
done and then finally there's the CPU that's

00:05:42.960 --> 00:05:49.919
tied to the eeprom and to the nand flash so for any recovery effort to be

00:05:47.440 --> 00:05:55.039
successful it needs to be working or at least mostly working a pretty

00:05:52.720 --> 00:05:59.759
famous internal story at drive savers is about an ipad that was pulled from a

00:05:56.960 --> 00:06:02.639
literal plane crash the board was so destroyed that it's a miracle they

00:06:01.199 --> 00:06:07.199
didn't just turn it away in the first place but after a full transplant as

00:06:05.280 --> 00:06:12.240
they call it they were actually able to get the device working enough that with

00:06:10.000 --> 00:06:17.120
clamps on the device to apply a little bit of extra pressure on certain

00:06:14.319 --> 00:06:20.720
components and by emailing the data to themselves rather than trying to

00:06:18.800 --> 00:06:24.639
transfer it over a cable which appeared to put too much strain on the CPU or

00:06:22.639 --> 00:06:28.800
something they were able to recover the needed flight recorder data one of their

00:06:26.639 --> 00:06:33.759
methods for these CPU transplants is rather ingenious i asked them why a cnc

00:06:32.000 --> 00:06:40.160
machine is part of their essential tool kit and it turns out that iphone 6 and

00:06:36.880 --> 00:06:42.400
6s have the RAM on top of the CPU with

00:06:40.160 --> 00:06:46.400
glue surrounding them so if you use too much heat the RAM can't breathe and

00:06:44.479 --> 00:06:51.919
it'll just pop or crack so get this depending on the device they

00:06:49.280 --> 00:06:56.639
can sometimes use the cnc to go in through the back precisely cutting away

00:06:54.479 --> 00:07:01.360
the logic board leaving only the exact dimensions of the CPU behind

00:06:58.880 --> 00:07:05.520
it's slower but it's a really clean way to do it and gives a higher success rate

00:07:03.520 --> 00:07:09.520
which is the most important thing they often prep their donor boards in the

00:07:07.120 --> 00:07:14.639
exact same way using their cnc from the top side to remove the CPU and RAM and

00:07:12.319 --> 00:07:18.960
expose the pads then it's a matter of aligning the solder pads from the old

00:07:16.240 --> 00:07:23.039
chip onto the new donor board that is a tough thing to get just right i actually

00:07:21.199 --> 00:07:25.599
tried that once with a macbook chipset in new york and

00:07:24.560 --> 00:07:29.759
well let's just say it's still dead

00:07:27.759 --> 00:07:33.440
fortunately drive savers is better at this stuff than i am and this kind of

00:07:31.680 --> 00:07:37.280
careful methodology has resulted in successful full transplants on even

00:07:35.759 --> 00:07:40.800
devices that have been driven over multiple times on the highway there's

00:07:39.360 --> 00:07:46.080
one that was dropped down a multi-story garbage chute that they pulled off and

00:07:43.440 --> 00:07:49.360
yes what i said before was true they actually managed to repair one where a

00:07:47.759 --> 00:07:53.599
gorilla like a real actual gorilla got its hands on

00:07:52.000 --> 00:07:58.639
the device when it was dropped into a zoo enclosure ironically though after

00:07:56.319 --> 00:08:02.319
all this drivesaver's biggest message in this sponsored video is

00:08:00.479 --> 00:08:06.639
back up your data so we never have to recover it whether it's on icloud a

00:08:04.560 --> 00:08:10.240
network storage device or a usb hard drive a second

00:08:08.479 --> 00:08:14.080
physically isolated copy of your important documents in media is the best

00:08:12.479 --> 00:08:16.720
insurance policy in the case of an unexpected disaster

00:08:15.919 --> 00:08:21.520
now common failures do come from user error

00:08:19.440 --> 00:08:26.080
like folks who think their device might be more waterproof than it is you know

00:08:23.520 --> 00:08:30.400
hey maybe if i just dip the the camera corner into the water drive savers has

00:08:28.080 --> 00:08:33.360
seen plenty of final videos like that but also don't trick yourself into

00:08:32.240 --> 00:08:36.159
thinking well i'm super careful it couldn't happen to

00:08:35.360 --> 00:08:40.959
me bad luck can happen to anyone and they've seen

00:08:39.120 --> 00:08:45.040
everything from phones that managed to slip through the crack in an elevator

00:08:42.880 --> 00:08:48.320
and fall all the way down the shaft to ones that fell out of a pocket and got

00:08:46.880 --> 00:08:52.240
stuck in the motorized reclining mechanism of a couch that's one that

00:08:50.240 --> 00:08:56.880
could easily happen to me my phone comes out of my pocket all the time their

00:08:54.320 --> 00:09:00.480
second message is to make sure that if you didn't pay attention to message one

00:08:58.880 --> 00:09:05.120
you're paying extra close attention to message two which is to only send your

00:09:02.480 --> 00:09:08.720
device to a trusted shop they've seen unrecoverable cases where if it wasn't

00:09:07.279 --> 00:09:13.600
for the ineptitude of a previous technician it would have been fine a

00:09:11.440 --> 00:09:17.440
classic example of this is iphone 6 screen replacements they had a case

00:09:15.680 --> 00:09:21.519
where a shop put a poor quality home button on a 6s

00:09:19.680 --> 00:09:25.760
plugged it in and shorted a resistor that on one side went to the home button

00:09:23.519 --> 00:09:29.279
and on the other side went to the CPU they did manage to dig out that trace

00:09:27.600 --> 00:09:33.600
and replace it but even though it was such a simple error that story

00:09:31.360 --> 00:09:38.560
unfortunately ended in heartbreak drive saver's process is to use the device as

00:09:36.000 --> 00:09:42.640
intended so a dead CPU that's a no go there's no substitute for

00:09:40.640 --> 00:09:46.160
expertise and that's kind of hard to get unless you're dealing with a lot of

00:09:43.760 --> 00:09:51.120
devices an example of this one was a weird update in the fall of 2019 where

00:09:48.399 --> 00:09:55.920
particularly the seven plus would get stuck on the apple logo which on the

00:09:53.200 --> 00:10:00.000
surface smells like a logical problem but then after seeing a bunch of them

00:09:57.680 --> 00:10:05.440
drive savers figured out that there was a physical fix by shorting the speaker i

00:10:03.120 --> 00:10:09.839
see that would somehow bypass whatever that logical problem was

00:10:07.440 --> 00:10:14.000
so then if they grabbed all the data unshorted a particular resistor then

00:10:12.000 --> 00:10:16.640
performed a factory reset and restored the data back onto the phone it was

00:10:15.680 --> 00:10:22.079
golden logical problem weird physical

00:10:19.279 --> 00:10:26.480
workaround so bottom line back up your data and if you didn't give drive savers

00:10:24.640 --> 00:10:29.920
a call they're well worth the money and after being the first to recover data

00:10:28.240 --> 00:10:33.440
from one they have over a decade of experience recovering iphones they don't

00:10:31.920 --> 00:10:38.240
even charge you unless they actually recover your data the consult and even

00:10:35.680 --> 00:10:42.160
the shipping to them is free if you guys enjoyed this video you might

00:10:39.920 --> 00:10:47.040
also enjoy a look at drive saver's hard drive data recovery process it's very

00:10:44.800 --> 00:10:50.880
very different and equally fascinating we're gonna have that linked below and

00:10:48.959 --> 00:10:55.480
we did that video a long time ago so it i was actually able to physically be

00:10:52.480 --> 00:10:55.480
there