Even if the OP is not, the rest of us are quite interested. Thank you for finding/researching/posting that info.
@trewmte
I am not sure to get it (actually I am pretty sure I don't get it) 😯 .
That "yankodesign" thingy is NOT a product, it is a design concept, and a design aimed to be a "portable/incospicuous" device to
- see what files are on a (flash) mass storage device
- transfer files from a (flash) mass storage device to another
[/listo]
BUT the original (nice) idea by Kkie21 was about imaging an Android device, and unless I am mistaken the main issue here is that you do not have access from the USB port to the internal storage of the device (and the - optional - micro SD card can be of course removed and imaged with *any* reader).
The "yankodesign" concept seems to me more similar to a "common" SIM or hard disk "duplicator" (with the addition of a slick design and the OLED display) a "cross breed" between this
http//
and this
http//
with some added (nice) bells and whistles.
I am failing to see the connection, what am I missing?
jaclaz
Bithead, thanks for your comments, appreciated.
Jaclaz… yes I think with respect you have missed the point. The earlier Towitoko device I mentioned identified that the manufacturer's original design (and confirmed) it had been altered to meet a new need. The design and "working prototype" of USB2USB as I understood it is not by Yankodesign but originated from "MIMOS Berhad". The purpose of mentioning the product was to extend to the OP (ideas/notions/inspiration) that a device can be altered to meet a need and here was a further example to consider.
I would be quite intrigued to see if an SD Card might hold a micro programme for imaging or the on-board chip could be (re-)programmed. And the hardware using USB at one end with another physical interface at the other might also be possible.
Jaclaz… yes I think with respect you have missed the point. The earlier Towitoko device I mentioned identified that the manufacturer's original design (and confirmed) it had been altered to meet a new need. The design and "working prototype" of USB2USB as I understood it is not by Yankodesign but originated from "MIMOS Berhad". The purpose of mentioning the product was to extend to the OP (ideas/notions/inspiration) that a device can be altered to meet a need and here was a further example to consider.
I still fail to understand.
From
http//
If only this wasn’t a concept and a reality, boy would our geeky lives become easier to share.
Chipdrive (the linked chipdrive.de) has developed a smart card reader with a LCD display that can read some contents of the smartcard and also write to it (with some firmware/software to do time/presence/accesses recording).
I am failing to see any evidence that the device preexisted as "Towitoko Chipdrive", I have seen "plain" smart card readers by Towitoko, called "Chipdrive" like
http//
http//
but they are seemingly completely different (and "dumber") devices.
There are a number of projects around Arduino
http//
Italian (but not that bad through google translate)
http//
The Yankodesign (besides being seemingly not even a prototype, only an exercise in design) is simply a (nice looking) duplicator with a viewer, something that can be easily made with - say - a RaspberryPI
http//
http//
And if you want to overdo it, using a touchscreen
http//
and a web interface
http//
I would be quite intrigued to see if an SD Card might hold a micro programme for imaging or the on-board chip could be (re-)programmed. And the hardware using USB at one end with another physical interface at the other might also be possible.
We do have some information on the chip (a 8051 compatible) inside some SD cards, see
http//
http//
http//
And the Wi-Fi SD cards seem like a lot more promising )
http//
http//
Though, if the idea is to have a display, most probably hacking a photoframe 😯 might be easier
http//
(good ol' 65c02 compatible inside) or maybe a MP4 viewer.
Hey, wait, maybe someone already thought of doing something *like* this wink (examples)
http//
https://
http//
http//
though not really on the cheap.
jaclaz
Jaclaz, you are merely identifying loads of breakout web-links which doesn't prove/disprove anything, merely you are reconfirming what you said at the outset that you don't personally understand. OK, this is fine.
It is the OP who is seeking ideas and doing the degree. I don't have to produce the tools or write the thesis for the OP and neither should you. And besides you're not producing the tool anyway…
The lead is there if the OP wishes to research thoroughly…will find the answers.
Jaclaz, you are merely identifying loads of breakout web-links which doesn't prove/disprove anything, merely you are reconfirming what you said at the outset that you don't personally understand. OK, this is fine.
Thank you for your kind acknowledgement of my right to not understand, that is very kind of you ) .
I provided "a load of breakout web-links" in order (hopefully) to expand on the specific topic which I perceived (wrongly) being about a (non-fictional) device that
1) is not a PC or tablet
2) has a display
3) has several different connections to different media storage devices
4) already does (or can be programmed/hacked to) copy contents of a device to another (which is the purported scope of the "design" you mentioned)
Notwithstanding the search I made, I could not find any evidence of a connection between
"Towitoko Chipdrive" and the device on chipdrive.de, if you have any data about that connection, please do provide it, that is the main point about "the manufacturer's original design (and confirmed) it had been altered to meet a new need" that I completely failed to grasp in your original blog post.
As well if you have any evidence of the USB2USB being actually (of having ever been) a "working prototype" I would like to know about it.
The other "loads of breakout web-links" were given to you in reply to your
I would be quite intrigued to see if an SD Card might hold a micro programme for imaging or the on-board chip could be (re-)programmed. And the hardware using USB at one end with another physical interface at the other might also be possible.
which I understood, evidently completely failing at it also 😯 , as a topic which you were interested in attempting to provide some related ideas/info/references.
As a side note and JFYI, years ago I have designed (actually dreamed of) a device similar to the USB2USB, which I called USB2ANY, only it was half the thickness, with stereo sound, could also act as wireless router and DHCP server, and convert from any filesystem to any other, powered by a button battery cell that is to be replaced every two years or so, and the nice part was that it could also make coffee, using water drawn from the humidity in the air of the surrounding environment.
I never went ahead to actually make a prototype because there was not enough space for the coffee and the sugar.
Sorry, I have to go, my hyper-super-turbo-califragilistic-hover-hyper (concept) car doesn't start (actually it doesn't exist) and I have to get the next bus.
jaclaz
I mentioned earlier on in this thread whether it might be possible for a micro program to be included on an SD Card. The idea may be feasible as a similar notion has been put into practice to logically extract files using a pre-profiled configuration file loaded onto an SD card and initiated at boot up.
MPE+ has a feature called dSOLO
dSOLO™
dSOLO™ allows you to provision a MicroSD card to extract pre-configured user data types from any Android device that has an SD card slot. With this mode, you can create an extraction profile containing the items to extract within MPE+ and then compile that profile to a MicroSD card. You can then insert the provisioned card into an Android device independent of any connection to MPE+. The configured application initiates on the Android device and the previously selected extraction capabilities are extracted from the device onto the SDCard in a format that only MPE+ can read. When extraction completes, you can read the SDCard containing the dSOLO data using the Read dSOLO Files option from the toolbar. Once the data is read, it is immediately available for preview, reporting, and analysis in MPE+.
Once an SD card is provisioned, you can use the same SD card to extract from multiple devices using the same profile without re-configuring the SDCard.
Requirements
Android USB debugging must be enabled
Computer's RSA fingerprint must be authorized (for Android 4.2 and greater)
Hi all,
Sorry I haven't replied to any posts but i'v been busy with other projects.
Thanks to all who posted on this subject.
After some thought I'm still interested in this project and a part of me still thinks that I will be able to get somewhere with it. Also, even if the project is not a success I will still be able to obtain a good grade providing I can include enough research and an explanation to whether or not it has succeeded.
@trewmte
Thanks for the links and the information on the USB2USB. Using a USB stick was my first thought due to the cost and ease of getting hold of one. I going to start looking around for some other devices which may offer more of a practical way to accomplish the task in hand. My only concern to using a different device is the cost as the high and more sophisticated the device, the emptier my pocket may become.
Also you mention about re-programming the chip set on the device. would this be a good idea in the forensics world? Altering evidence would cause problems when presented in court?
@jaclaz
Thanks for all your interesting links they have been a great read! You mentioned in one of your posted about not having access to the internal storage from a USB. I'm thinking this would be one of the biggest hurdles. You also mentioned about loading a program onto a memory card which again, would this not be classed as altering evidence?
I am going to have a play around with some Java programs and load the onto the USB and see what I can achieve.
Thanks again to all who posted and all the research and help that has been provided.
Kkie21
[quote="Kkie21]@trewmte
Thanks for the links and the information on the USB2USB. Using a USB stick was my first thought due to the cost and ease of getting hold of one. I going to start looking around for some other devices which may offer more of a practical way to accomplish the task in hand. My only concern to using a different device is the cost as the high and more sophisticated the device, the emptier my pocket may become.Kkie21
Well good luck in searching.. Understand about the issues with keeping costs down.
[quote="Kkie21]Also you mention about re-programming the chip set on the device. would this be a good idea in the forensics world? Altering evidence would cause problems when presented in court? Kkie21
I meant re-programming the tool I had mentioned as opposed to the actual evidential DUT.
However, loading a client/agent onto evidential DUT is not uncommon. And there are varying ways to do this. I am working on the assumption based upon your comments above that you may not be aware of the following
1) Examiners loaded client/agent onto some early Nokia devices in order to extract and harvest data. As part of your research for historical references, examples of useful forums to conduct searches for answers are
a) http//
b) forum.xda-developers.com
c) http//
The client/agent was known to add data to the evidential DUT identifying the communication path activity used for transporting data to the examination tool.
2) I would recommend your research to include searching in the known examination tool manufacturer/producer manuals. For instance, one known manufacturer states in their manual regarding data extraction
"Client/agent A client is used during logical extractions. It is a very small application that is temporarily installed on a limited number of Android, older Windows Mobile, Palm OS, and Symbian models. The client is unlike a boot loader in that, rather than be installed to the device RAM, it acts like any other third-party app by installing to the device ROM. It does not overwrite any data; it will not install, for example, on a device whose memory is full."
3) I would recommend regarding boot mode that you also search for and read "Passe-Partout a General Collection Methodology for Android Devices" by Daniel Votipka, Timothy Vidas, and Nicolas Christin, Carnegie Mellon University.
I have purposefully identified information above specific to your proposed project but allowing you to research on your terms.
I do see the point about a USB tool and the entire operation of imaging/data extraction being e.g. booted from the USB device. One matter I would raise is having sufficient memory on the e.g. USB stick for capturing the image output from the evidential DUT.
@Kkie21
The point I was trying to highlight was that nowadays a "normal" Android device is configured (in factory) in such a way that it only boots from the internal storage.
Specific make/models workarounds may well be possible, but it is unlikely that a generic one will be possible.
A change (that a lot of people hated (as it limits quite a few previously possible uses) and a lot of people praised (as it somehow increases security)) somewhere in the way Android "core" works, see (only seemingly unrelated)
http//
http//
Basically the issue is that *whatever* is running on the "internal" Android lacks access, so *somehow* you need to boot or execute *something else*.
The nice dSOLO™ thingy trewmte mentioned is a very good idea/device, but its requirements
Requirements
- Android USB debugging must be enabled
- Computer's RSA fingerprint must be authorized (for Android 4.2 and greater)
are in practice rare to fulfill.
IF you have USB debugging on, it should mean that you already have access to the device and you can do from it a whole lot of different things normally impossible.
jaclaz