[Q] Imaging the File System - Touch Pro, Fuze General

I am working on a project at working concerning the HTC Touch Pro (Fuze) running 6.1. We are looking to take a forensic image of the device from the file system up. Our traditional software for imaging other types of drives (hard, flash, etc.) can only see the existing files on the device. We want to be able to perform a full acquisition.
I know this is possible on Android devices, I've spent a lot of time doing it. On Android devices I am able to use Android SDK/ADB to copy the mmcblk files from the device to the host computer.
I have the Windows SDK in Visual Studio. Is there something similar to ADB for Windows? I basically just need a command-line interface with which to communicate with the phone.
Any information would be appreciated!

mpercy725 said:
I am working on a project at working concerning the HTC Touch Pro (Fuze) running 6.1. We are looking to take a forensic image of the device from the file system up. Our traditional software for imaging other types of drives (hard, flash, etc.) can only see the existing files on the device. We want to be able to perform a full acquisition.
I know this is possible on Android devices, I've spent a lot of time doing it. On Android devices I am able to use Android SDK/ADB to copy the mmcblk files from the device to the host computer.
I have the Windows SDK in Visual Studio. Is there something similar to ADB for Windows? I basically just need a command-line interface with which to communicate with the phone.
Any information would be appreciated!
Click to expand...
Click to collapse
I think MobilMon can monitor file system activity and allowing them to keep a log on device

Related

Android?

Any chance of someone or a group of great developers putting together android in a format like ubuntu that can be loaded onto the device in question through USB. Ok hear me out all that ubuntu does when installing is configure itself from a compiled database of your hardware specifications. So there are only so many devices out and only so many drivers to run those devices hardware, could we feasibly compile all of them and put them in with an android installation thatr ran from the host computer and installed itself according to what the computer told the installer to do if the computer reads that you have a specific chipset with a 1ghz processor it loads in the files and commands for that and so forth, just an idea, its gotta be possible right? its just an miniature OS............

Question related android ?

i just want to know that why android operating system does not work directly in mobile devices
why there is need of development in it to use in all diffrent phones?
why it cant work directly like windows in pc does
and other question all others like bada os, symbien and apple os they all need they also need development or we can use them directly
if sumone didnt understand my question i will explain more
for further explanation>
windows we can install directly in any pc of any company or assembled
but android need development and designed for a seprate product of a specific brand
why?
no1 is intrestd in answring these questions ?
You are just kidding here right?
/Pun intended.
For example
[1] ....
[n] Windows has the complete set of drivers
[n+1] The manufacturer delivers the driver
Fundamentally, you're misunderstanding the situation. Windows does not run on any computer you can throw together. It runs on any computer that you can throw together that matches the evolving, de facto standard that started as the IBM PC.
It won't run on a SPARC Station or a 68k Mac or an IBM 360 or a Wii or a PS3 or, well, a HTC Vision.
Similarly, Android will run on any PC, er phone, er tablet, er, well computer that is basically the same as an existing Android device. The vast majority of the custom development that is, strictly-speaking, necessary for a new device amounts to device drivers. Now, most manufacturers do a lot on top of that to distinguish their product. That's where Sense and MotoBlur and such-like come into play.
A further complication is that storage space and memory are at a heavy premium on these devices. So, it is infeasible to include the incredible variety of drivers and other hardware support that makes a typical Windows or Linux install need several GBs.
Back in the day, when dinosaurs roamed the earth and there were only a handful of PC makers in the world, similar customization was needed. My first PC came with a manufacturer-custom version of DOS 2.1 and Windows 1.1. Is wasn't until at least DOS 3.x (maybe 4.x, that was a long time ago) that a vanilla MS copy had a chance of working. Even then, most peripherals *needed* a custom driver to be used at all. My first mouse is an example. Only way to use it was the Genius Mouse drivers that came with it.
thanks for ur answers guys

What is ADB [Explained]

When it comes to Android modding, most novice users are confused or left wondering by reference over reference to a certain “adb”. This is specially true when you are looking up something on modding your device, or root it in particular. ADB is the wonder toy of Android and everyone seems to love it, so lets have a look at understanding what it is and why you need it, and how you can get it.
What is ADB
ADB stands for Android Debug Bridge. It comes as a part of the standard Android SDK, which you can grab here. Basically, it provides a terminal-based interface for interacting with your phone’s file system. Since Android platform is based on Linux, command-line is often required to perform certain advanced operations on your device using root access.
While these things can be done directly on the device itself using some terminal emulator, it will be rather difficult to execute complex commands on such a small screen. ADB provides the bridge between your machine and your computer.
Read full post : http://dreamproject.asia/faq/terms-slang/what-is-adb/

[Q] Mobile Device Forensics

Looking for developers who can help bring this project to life.. and general discussion of how it could be done.
In the computer forensics field, when you want to see what the system was running, you make a forensic image of the hard drive (which is a bit by bit copy of the entire hard drive) and use that image file in a virtual setting to boot the machine..
I can obtain complete physical dumps of cell phones (most anyways) but how can I now virtualize that BIn file to see how the device looked to the user? What was on their home scree? icon placement etc?
The main reason to run with this in a virtual environment is that it is hard to set up a test phone to the exact specs of the users device..
So how can this be done using SDK development tools or would you need to build an program from the ground up?
Ideas?
Thoughts?
has this already been done and I am just not aware of it?

[APP][open source] UMSMounter - host ISO/IMG files to boot your PC from

[Android 4.1+][ROOT]
As a heavy user of DriveDroid I noticed that development has stalled recently and my device was is supported anymore.
So I tried to make my own app with the same functionality:
UMSMounter allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go... without the need to burn different CDs or USB pendrives.
USB Mass Storage (UMS)
UMSMounter relies on the kernel of Android, in particular the USB Mass Storage (UMS) feature. It allows your phone to act as an USB-drive and have a device (SDcard) or file (ISO/IMG) be used as the content for that emulated drive.
Different Android devices implement this feature differently. Most modern devices do not have UMS enabled by default, but it is supported by the kernel.
UMSMounter also includes a convenient download menu where you can download USB-images of a number of operating systems from your phone.
You can also create USB-images which allows you to have a blank USB-drive where you can store files in. Another possibility is to use tools on your PC to make a bootable USB-drive out of the blank image that UMSMounter created.
In particular, I added configfs support (Android moved to ConfigFS based USB gadgets for their newer (android-3.14+) kernels.).
Unfortunately, my phone's display is broken now, so I am using my old Galaxy Alpha (SM-g850F) again. So official support is only for that device.
I hope to support more devices, but I am not able to test - so I rely on your support!
There is a high probabilty that it won't work on your device, but if you send the crash report I will see what I can do!
For that reason I made an apk that is integrated with firebase, so if the application crashes I can immediately see the crash report.
I decided to make the app open source, because I don't think interest is big enough for me earning real money with it, so if you want to, please contribute.
I'm relativley new to android development and it will probably show in the code - I'm very open to improvement suggestions
(also, there is no documentation and very few comments. It started as a personal hobby project)
Any feedback is encouraged!
Downoad: app-release-firebase.apk
Source: github
Screenshots:
thanks for making this. im going to give it a try since my moto x4 doesnt work with drivedroid
Any update on your app? can it work on Android 13?
euphoria360 said:
Any update on your app? can it work on Android 13?
Click to expand...
Click to collapse
Works on Pocophone F1 Android 13 kernel F1-10.3.7-SE-NoGravityKernel-4.3.1
I created 5000MB image in external microSD then mounted it ,pluged phone to computer and device appears in Windows explorer (empty FAT32) then put all files from Windows 11 ISO inside device (very slow).
Successfully booted this Windows 11 installation to another computer.

Categories

Resources