Database Develop

Encryption & Presenting Unencrypted Data over USB Mass Storage

I'm considering getting an N1 and I would like to be able to encrypt files; a blog post titled "Android + encryption on the G1 using cryptsetup and LUKS" (I can't post links) seems to indicate that I could get LUKS encryption to work. Would that cross-compilation procedure result in a working binary for a rooted N1?
Secondly, would it be possible to present the unencrypted block device to a USB host over USB mass storage? I'd like to be able to view the encrypted files on a Windows computer without installing anything extra or typing any passwords into an untrusted computer.
I would like to note that I found this to be possible with my current WM6 Standard smartphone using a recompiled version of FreeOTFE4PDA and WM5torage.

[Q] Capture image of a X8 internal memory

I am interested in creating a forensic image of a Xperia x8 internal memory (school purpose). When I connect the device with the USB cable I can only see the SD card partition. I tried with different tools: ProDiscoverer Basic, WinHex...
How can this be accomplished ?
I don't want to root, install a particular app or alter in any way the content of the internal memory, that will ruin the hole ideea of a forensic image..
Oh yeah.. on previous owned devices: SE Elm or SE Z520, after connecting the device I did have access to the internal memory.

Connecting the device in USB storage mode won't get you any far. That way, as you already worked out, you only gain access to the SD card contents.
You actually need to look into the "adb" commandline tool that comes as a part of the Android SDK (if you look around on XDA you will find adb.exe plus the two required DLLs so you don't need to install the whole SDK along with the Java JDK).
The problem you will face:
If the the phone isn't rooted you won't be able to gain access to all parts of the internal file-system (i.e. some directories may appear empty though there are files and directories inside).
Apart from that - that's not a approach fit for forensic analysis.
IF you would want to tap into a device that's up for forensic investigation the worst thing you can possibly do is to actually turn the device on, let alone boot it up. Chance are that this could destroy valuable evidence (don't take everything you see in CSI:Retards for real) or trigger a "killswitch" that could delete data.
To perform a real forensic analysis you would actually take the phone apart and tap into the system through the JTAG interface. There you are talking directly to the hardware without the phone being booted or even "turned on" (it'll just sit there in "standby-ish" mode).
From there you would then dump the contents of the NAND (the internal memory of the phone where the Android OS, data and installed apps reside) into a file on your computer to perform further analysis.
Once the content of the NAND is secured you can crack down on the SD card (to secure further data for investigation) by slapping it into a card reader being WRITE PROTECTED and do a dump of the SD into a image you can then later mount or hex-view on the computer.
In other words ... to "emulate" a forensic analysis (by ignoring the fact to break basic safety measures) you would actually need to ROOT the phone. Once you did that, and therefore have busybox and su in your ROM, you can then use "mtd_utils" to dump the nand into a file for further analysis.
EDIT:
MTD Utils (i.e. dump the content of the NAND)
These files need to go onto your phone! This are NOT executables for Windows or Linux desktop PCs!
ADB (Windows, Android Platform Tools r10 at the time of writing)
Download the ZIP and extract it ... you only need adb.exe, adbwinapi.dll and adbwinusbapi.dll
Do NOT forget that the Android drivers for your phone need to be installed!

Thanks for the answer. Do you know/have any links regarding what cables/connectors or other hardware tools I need to tap into the system through the JTAG interface.
I found a link:
gsm-technology.com/index.php/en_US,details,id_pr,8466,menu_mode,categories.html
.. dude has a lot o hardware equipment and cables... where can I get & buy stuff like that?

I would try eBay first - or look into finding online retailers selling you a RIFF Box plus required toolset.
Since you said it's for a study project I'm not sure if the equipment you need to really replicate a "professional forensic analysis" will match your budget. A RIFF Box usually goes for USD 150+ over the counter, and then you need some experience to get it to good use and also know a thing or two about electronics in general.
EDIT: Well, the link you posted is the JTAG Header adapter (for the X8 and possibly also W8). If you scroll down they also have the RIFF Box for EUR 119,00 enlisted. And it seems that's actually a online retailer where you could buy the stuff.
---------- Post added at 11:12 AM ---------- Previous post was at 11:02 AM ----------
Ok, to pull it together ...
Xperia X8/W8 is based on the MSM7227 CPU, hence you need ...
Medusa JTAG Box EUR 119,00 (w/o VAT)
Supports MSM7227 based devices. Cables come with the box.
JTAG Xperia X8 EUR 8 (w/o VAT)
That's the JTAG header adapter
Apart from that you may need some software and a good idea about how to wire the cable from the Medusa Box to the pins on the JTAG adapter. Chances are you may also need a power adapter to power the JTAG (if powering the phone through USB doesn't work).
EDIT: Forgot: While the Xperia phones aren't really listed at the RIFF Box that box should work as well.

[Q] Can someone please help with USB connection?

Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?

bullpen7979 said:
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
Click to expand...
Click to collapse
you can push adb when the phone is connected as a camera. To connect it via ptp, you just scroll down your notifications bar and click on the usb notification, you can switch to ptp there. But like i said, adb works when connected as a camera device, so you are doing something incorrectly with adb. Possibly the commands you are running. The OS for your computer might be causing the problem (but that would mean oyu have the wrong stuff downloaded to adb with the computer set up you are using). You don't have the correct drivers. You are using a faulty data cable. you are using a usb 3.0 port that isn't compatible. it is an endless list. Also, you can copy stuff to your device in camera mode as well.
also would like to note that whether you phone is rooted or not has nothing to do with your ability to use adb or push files to your phone.
finally, this is a question which should go under q&a not the general discussion subforum.

I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.

bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
so whats the problem. you have adb working. What do you mean you can't copy things to the phone. What error do you get when you try to push a file to the sdcard on the phone? You see your phone in the list of devices so you can put files on it that way too. Really confused at your dilemma.
you trying to root? you trying to push files to the phone? IDK, but you clearly should be able to push them if you have adb running. Perhaps you aren't running the right commands to push files to your phone.

Don't you have to have USB debugging on?
Sent from my XT1060 using Tapatalk

bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Click to expand...
Click to collapse
Unless you have another android device connected to your computer, your X has USB Debugging mode turned on, and Windows & ADB properly sees your phone.
As jayboyyyy posted, in this state you can use ADB to push files from the PC to phone, or pull files from the phone onto the PC, assuming you are using the right commands. But if all you are looking to do is copy files back and forth, this is overkill as you can do it with windows. ADB is usually only need for hacking and flashing your phone.
As I said in the other thread... Please include what you were doing and what the results are. You haven't given us a complete enough of a picture to understand 1. what you are trying to do. 2. Any/all steps you have taken. 3. EXACT error message you are receiving.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader. But your second paragraph starts saying you can't get the thing rooted to save you life.. So which is it? Are you rooted or trying to root? If you are trying to root, what process are you trying to follow? What step in that process are you stuck at? What did you type and what did you get back?
I know you are probably frustrated, but its just as frustrating on this side when you don't give a complete picture that allows us to help you. Look, rooting and hacking isn't easy. It can even result in turning your phone into a paper weight. So these details are important so we don't screw things up and add to the headaches and frustrations.
bullpen7979 said:
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
I'm not sure what you are doing, or trying to do, as you said in the first post that you unlocked the boot loader and rooted.
The Moto X wont show as a drive letter in "My Computer." Even if USB Debugging is on, it should show up as a "Media" device, or Player type device with an icon in a separate section from your hard drives, DVD drive, mapped network drives, or even USB memory sticks/flash drives. It does this because the X supports/uses MTP/PTP, and NOT USB MASS STORAGE MODE.
MTP/PTP wont show a drive letter in My Computer. This is by design. You don't have to "stop" or "eject" the phone from windows when you are done. This mode also allows the phone to access the "storage" or emulated "SD" partition at the same time a connected Computer can.
USB Mass Storage mode will give you a drive letter in My Computer, IF the phone supported it. However the X doesn't, at least not out of the box, and I'm unaware of any app or hack to enable this. In USB Mass Storage mode, the PHONE looses access its storage partition or emulated internal SD card while the PC is connected. You'd need to "stop" or "eject" the device when you want to disconnect form the PC in order to prevent data corruption of the "emulated SD"
So again, its important for us to know exactly what you are trying to do.

From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader.
Im sorry I was unclear. Bootloader is unlocked, but I am not rooted. What I said was that I had another thread about getting it rooted.
I'm sorry for the mis-speak. And I'm sorry I'm being such a pain, but others in the thread I'm referencing are clearly having the same issue I am. I just need to know what to do to obtain root access if my bootloader is already unlocked. To be clear, I do NOT have root access.
This is my procedure.
Start with this link:
http://forum.xda-developers.com/showthread.php?t=2509676
Download Cydia Impactor. Check.
Download RockMyMoto.zip attachement. Unzip two files to directory x. Check.
Download PuTTYtel file "puttytel.exe" Check.
Step one. I have my ip address. At bottom of wireless config on phone, it is 10.59.1.6. So far so good.
I run adb shell getprop dhcp.wlan0.ipaddress just to be sure. same ip addy. Good.
I start command window. push the two files to the phone. all is well.
Step two i open the puttytel window and proceed to run the exploit
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
and I can't run the damn thing because i get PuTTytel Fatal Error
Network Error: connection timed out.
exactly like this dude: http://dl.xda-developers.com/attach...f04a/5290120c/2/3/8/1/6/0/9/1384014224630.jpg
The end. I read the rest of the thread, and post #22 is the first of about five other posts that mentions the same time out problem, a solution for which is NEVER ADDRESSED, except indirectly as a possibility that the the two devices are not on the same network. My wireless card is on dhcp and the phone is the IP address above.
that's where it stops. I can't run the exploit because i can't type the command fast enough. Several people mention this problem, but I read all SIX pages of the thread and this defect is experienced my many and adressed by nobody.
This is driving me stark raving Bat S#!+ crazy.

And yes I have USB debugging on.

If your boot loader is already unlocked, there is another process.
https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Is the process and while I think that twrp version should work, you might need the older version. Had to take my mom to the hospital so not in a good position to find older if newer doesn't work.
EDIT: this thread -> http://forum.xda-developers.com/showthread.php?t=2536200 has some discussion too

[Q] Unable to connect to Mac w/ Remote Storages via File app

Hi everyone,
I appreciate any help you can give "the newbie" here.
I swear I'm not a total moron, but I can't get this to work. I've tried searching the forums and google, and I've found posts with similar problems, but no solutions. Until I can get another computer to test this on, I don't know if the problem is with my Droid Bionic (unrooted, running JB stock 4.1.2), or my computer (Mac OSX 10.8.3) or my modem.
I would LOVE to root my phone, but I can't even get the darned thing to connect to my computer through the file app!
The phone is on the same wifi network as my computer. Both have no trouble accessing the internet. Both can ping each other (packets sent and received fine). But I can't connect one to the other.
I turn on file sharing on my computer with SMB only
select a folder on my computer to share
Assign a user and password permission to access that folder
make sure permissions for that folder are set to read and write
then go to my phone, open the stock file app
Select "Remote Storages" and "add storage"
Then I enter the IP address for the computer
WORKGROUP for the domain name
The name of the shared folder
The user name and password
then I try to connect.
And I get an alert box on the phone that says
"Network Error
There is a problem in your network connection with remote host. Please repair your network connection and try again."
I'm doing everything that's obvious to do, so I'm guessing there's something "not obvious" that I'm missing. - Anyone here had a similar problem and solved it?
Some things I've tried:
Moving the shared folder to different directories including root, desktop, and "public folder" (each time I moved it, I removed it from the shared list and re-added it)
Creating a guest account and allowing it access to the shared folder - no password needed
Creating a 2nd admin account and allowing it access to shared folders (password)
Turning off computer's firewall
Seeing if I could connect through the computer and phone's browsers (no go!)
Lots of turning things on and off (sharing, users, permissions, wireless...etc.)
Gone into recovery mode on the phone and done a factory reset and wiped the cache partition.
When I check my modem's admin page, I can see both the computer and phone listed there as connected devices. The modem sees them both, and they can ping each other. Why the heck can't I connect them to each other?
Oh, and though I don't think this is relevant, when I connect via cable in USB Storage mode, I can see the internal and external cards on my Mac just fine. They both mount as drives and I can drag stuff back and forth. - Wish I could find instructions to root THAT way!
I finally get the nerve to try to root this and get it on TMobile, and I can't get past the part that should be a no-brainer!
Any help would be appreciated.
BB01
-------------
Editing on 1/8/14 to add that the problem may be related to a Samba issue in OSX Mountain Lion. I'm also wondering if it could be an issue with my modem, which is several years old. I'm going away for about a week so I may try this on a friend's computer. I'll report back WHEN I am successful with this (because I will be!)

Can't root through Mac Mountain Lion. Use Easy Root in VB
Replying to my own post, to follow up. I was unable to connect through samba on my mac running Mountain Lion, while at a friend's house. So the problem was not the modem, but my OS itself.
I'd read that Easy Root ( http://forum.xda-developers.com/showthread.php?t=2256439 ) using Virtual Box hadn't worked on a Mac, but I decided to try it anyway. I had to change one setting in Virtual Box from NVidia to "en1: Wi-Fi (AirPort)", and then the Easy Root worked flawlessly. When it got to the part about connecting the Bionic to the Remote Storage folder, I thought "Here we go... this is the part that won't work!" but with Easy Root running in Virtual Box, the bionic connected to the shared folder perfectly.
Mac users with Mountain Lion or above, use Easy Root in Virtual Box to root your Droid Bionic running Jellybean 4.1.2 (here's the link again: http://forum.xda-developers.com/showthread.php?t=2256439 ). I know there are posts by people who were able to root their droids through the Mac terminal, but I'm guessing they were on an older OS where smb still worked correctly.

Simple explanation to fix ADB unauthorized device in 'M'

QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.

Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.

Are you running the latest adb/fastboot tools on your PC?

Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/

I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.