Investigators Should Be Able To Access Trayvon’s Phone

Photobucket

While I still await that longed for day when evidence is shown that the phone found at the scene belonged to Trayvon Martin other question can be answered. Looking back at the original report from the SPD officer who first investigated the phone, Officer Santiago, I discovered he had misspelled the name of the company of the maker of the device used to access cell phones. Santiago spelled it “celabrite” but the actual spelling is Cellebrite.

Photobucket

Photobucket
http://www.cellebrite.com/mobile-forensic-company/about-cellebrite-forensics.html

Looking into Cellebrite further I can see no reason why investigators could not then or now easily access the phone.

First, Cellebrite claims their devices can bypass any type of lock;

Photobucket
http://www.cellebrite.com/forensic-solutions/android-forensics.html

So that takes care of that issue.

Second, the phone found at the scene is identified as model #U8150 which is a Huawei IDEOS phone.

Photobucket

Photobucket

In Cellebrite’s Supported Devices Excel download we find a listing for that particular device;

Photobucket
http://www.cellebrite.com/mobile-forensic-support/ufed-supported-phones.html

Photobucket

Cellebrite added access for that phone in 2010 so there’s no issue there and as such I can not understand why the SPD, Seminole County Sheriff’s Office or FDLE have not been able to fully access the phone. Any subpoena’s then are unnecessary to fully access the phone.

Accessing the phone should be somewhat similar to the video below;

Advertisements

15 thoughts on “Investigators Should Be Able To Access Trayvon’s Phone

  1. Officer Santiago: “…could not download any information because …was not operable because the cell phone had gotten wet”

    How do we eliminate that from being the problem that is preventing download?

    • I suppose we can’t eliminate that as a possibility but later they were able to get some info off the phone and because they said it was a lock preventing them from getting in the phone which implies they ought to be able to get passed that lock with this technology.

      Another possibility is that investigators were using dated cellebrite machines but I find it difficult to believe that at least the FDLE is not up to date on that.

  2. I believe some months ago that Jello333 had left a comment at GZlegalCase & shared the reply he received at that other site. There’s a good probability that the defense team will seriously consider sound suggestions. Robert Zimmerman would be another venue to submit useful suggestions in hope that the defense team is aware of probable worthy information

  3. If the issue was that the phone got wet, pull the battery, stick it in a bowl of white rice, and let sit overnight. So long as the phone was not shorted out, that would work. Then is simply a question of getting a new battery or powering via the USB port via a computer or some other device. This is not rocket science. The Cellebrite device could pull the data no problem once the phone has dried. Either they did not try, or they are withholding the records from the Defense as to what the ultimate results were.

  4. What is available that assures us the phone is not permanently damaged?

    Was not a 911 call made from that phone after it had been recovered?

    Diwataman provided the data necessary to suspect something corrupt is going on with that phone.

  5. Doesn’t it say that the extraction only works if usb debugging is turned on? If it’s not it wouldn’t work.

      • I am confused why USB Debugging could A) not be manually enabled, or B) assuming that the phone could not be accessed, it could be put into Android OS’s Download Mode, and a kernel flashed to the phone with USB Debugging set to Enabled. USB debugging it turned off as a default, and most basic Android users have no need to enable, so they do not. Only if the user is advanced, and roots, and/or flashes ROMS and kernels, would they have need to enable USB Debugging to get access to overwrite the Stock ROM. Turning USB debugging on would not be a showstopper in any scenario I can envision.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s