How to get UMS (for FAT32) only with PC manipulation ? - G1 Android Development

Hello,
I'am looking for a solution to get the FAT32 partition access as an USB mass storage only by manipulating my PC (of course, after pluging my G1 on USB).
I don't want to use the notification system on my G1.
Through an adb command for example...
A perfect solution would be : an icon to mount, and another icon to unmount.
Any idea ?

I'm not so sure about this one. I'd imagine it would involve a script that begins running adb and mounting your Android's SD card through adb. THEN you'd have to have another icon that recognizes the currently mounted drive and unmount it. I could see how you can associate your SD card to only show up as a certain drive (I have mine set to always come up as the "B:" drive), but there's so much communication involved between your phone and PC it leads me to believe the rest of the process to be an impossiblity. You're sure asking your PC to do a LOT. Considering what you want this "program" to do, it's hardly worth the effort to even attempt writing it.
Simply put, it's like trying to train your dog to unlock and open your house for you when you come home instead of simply using your house key.

PartEdMagic is your key to a FAT32 formatted microSD card
The easiest way to FAT32 your SD card is to boot up your PC with the "gparted Magic" ISO/CD (can do in vmware even), mount your SD card (via phone may work, I used a micro-SD USB card reader) - delete your partition on the SD card and recreate as FAT32, then format it. All can be done in PartEd Magic.
Hope that helps
[email protected]

mattrophy:
... i don't think he wanted to format it
Christopher3712:
Asking his PC to do alot? This is in no way a hard task, it requires 2 calls to adb, thats all...
koxx:
To mount it from your pc run: "adb wait-for-device shell sdutil ums enable", and to unmount "adb shell sdutil ums disable".
So, if you want 2 icons doing that, just make a shortcut that executes the commands above (either with the full path to ADB, or with adb's directory in your PATH var).

Joushou said:
mattrophy:
... i don't think he wanted to format it
Christopher3712:
Asking his PC to do alot? This is in no way a hard task, it requires 2 calls to adb, thats all...
koxx:
To mount it from your pc run: "adb wait-for-device shell sdutil ums enable", and to unmount "adb shell sdutil ums disable".
So, if you want 2 icons doing that, just make a shortcut that executes the commands above (either with the full path to ADB, or with adb's directory in your PATH var).
Click to expand...
Click to collapse
Exactly, I don't want to format my card ... it's already done
Your command works fine ! Thank you very much !
To finish, do I need a windows command to synchronize data before unmount UMS ? (equiv of "windows unmount" operation)

Related

[Solved] Formatted SD Card will not mount.

I just formatted my SD Card through the settings menu and now it won't mount. When I hit "mount" it says "Preparing SD Card" in the notification bar, followed immediately by "SD Card safe to remove" and "Blank SD Card."
Anyone know a way around this? I can't use so many apps because they require the SD card
Edit: I solved this by putting the card on a camera. It magically reappeared.
format settings
hey at first on which phone ?
and have you tried formatting the SD at the pc @ FAT32 ?
greets
It's on a mytouch 4G with cyanogenmod 6.1 and I can't mount it on the pc (windows 7 x64) or right click anything to format because it won't recognize it. I've tried a lot from other threads and google searches like uninstalling and reinstalling the disk drive driver in device manager and rebooting everything and doing multiple battery pulls :/
Try this:
VanKlomp said:
To fix the SD cards I booted into Ubuntu Linux, opened terminal and then;
1. Boot into Linux
2. Open Terminal
3. type 'sudo killall hald' and press enter
4. type 'sudo dd if=/dev/zero of=/dev/sdb' and press enter (this took about 20 mins per card)
5. Used GParted to recreate the MBR and format the volumes.
Click to expand...
Click to collapse
Worked for me.
I don't have Linux..

[Q] internal sd card for samsung captivate shows as write protected

I will give some background to begin with. I had installed the Kies mini update to the 2.2 software on my Captivate. I then rooted with super one click. I have the drivers for the Captivate installed in Windows XP and I have USB debugging enabled. It recognizes the drive and will show me the contents on the computer, but it doesn't allow me to copy from the computer to the drive. I know I can use dropbox for some things, but for other things like installing a custom rom, I would like to be able to copy to the drive. It does show as mounted and mass storage is enabled on the phone. Any ideas?
If you are rooted just go into cwr and mount sd card there. if not i have no idea as i haven't kept a phone stock since a week after i got my old Moto Droid, as soon as i found out it was possible.
Well apparently the version of Clockwork Mod Recovery that I have doesn't give the option to mount the SD card. I have 2.5.1.2. I did find a way using SGS tools to download a custom rom to the root of the SD card. I was going to reinstall Debian Linux at some point on my computer so I may have better luck with using that to write to the SD card then I am having with XP.
Yeah
Make sure that the SD card isn't locked. Also, back up everything on it to your computer and do a complete format as well. And if you're wanting to write ROMs to your SD (or CWM, etc.) in Linux, you're going to have to use dd in the terminal, and most like will be writing to "sdb".
Here's a simple walkthrough just in case you don't know how to use dd:
Become root by typing "su" and following it with your password. If you don't have a root password, type in "sudo passwd" and set it.
Next you have to unmount your microSD. To see what you have mounted type in "mount". Your SD card will most likely be called "/dev/sdb" or "/media/sdb" or something along those lines (not sdb1, that is the partition on the card). Once you know what your SD is called and where it's located, type in "umount /dev/sdb", placing '/dev/sdb' with the actual location and name of your SD card.
Now we get to use dd. Type in: dd if=<insert location of IMG here without the tags I included> of=<location of your sd without the tags I included> bs=1M
Be patient, because it usually takes a while, depending on what you're writing. Good luck mate.
I was looking for an answer to this myself. Me and my girlfriend both have the same phone, galaxy S. We both put andromeda rom on it and are now going to switch to FireFly (I did, she's trying to).
Well, mounting her USB storage ends up with the internal SD card being recognized as a CD ROM and the external as a usb storage device.
Anything we try to do to her internal says there's write protection and to disable it or use something else every time we do anything.
Only even trying this because we're getting some weird "Error at line 17: symlink with SU..." blah blah....
Completely stuck here. Doesn't make any fracking sense.
same to me. what should i do? I'm trying to install Andromeda. But I can't even copy ROM file to internal SD card. HELP ME ASAP!

[Q] How to mount internal sd card in usb storage mode (for data recovery)

I made a mistake yesterday to wipe the internal sd-card in twrp recovery. There is some data on it which I want to recover (read: undelete). Data recovery itself won't be a problem, but I have troubles accessing the internal sd card from PC.
There is currently no rom installed on my tf (I don't want the internal sd being touched by anything until I recovered data).
I thought it was possible to set the tf101 in USB mass storage mode in the recovery, mounting the internal SD card, but that refuses to work.
What I've tried so far is enabling USB Mass storage mode in a variety of recoveries
- initially in TWRP recovery (v2.2.X.X not sure which version was installed, probably 2.2.2.0)
- cwm-6.0.1.4-notouch-hybrid.zip
- Rogue XM Touch Recovery v1.5.0-R1
- TWRP 2.2.2.1 (flashed by replacing the recoveryblob in a flashable zip from 2.2.0.0 version)
But it seems not possible, i.e. no drive is detected by Windows or Linux machine.
What is the correct way to access the internal sd card over USB?
./adb connection will set you free. as long as you can get an adb connection this is not a problem. once youre connected just rtfm ./adb will pull up all the options.
haxin said:
./adb connection will set you free. as long as you can get an adb connection this is not a problem. once youre connected just rtfm ./adb will pull up all the options.
Click to expand...
Click to collapse
Thanks for your reply.
I'm able to connect through adb. I can access the internal sd card through adb shell. However, I need to have access to it outside adb, so I can use a data recovery tool to access the internal sd.
I still cannot find a solution, not for ICS. (this solution doesn't work for ICS).
Is it possible to enable UMS from ADB or recovery at all?
Tutti-frutti said:
Thanks for your reply.
I'm able to connect through adb. I can access the internal sd card through adb shell. However, I need to have access to it outside adb, so I can use a data recovery tool to access the internal sd.
I still cannot find a solution, not for ICS. (this solution doesn't work for ICS).
Is it possible to enable UMS from ADB or recovery at all?
Click to expand...
Click to collapse
when you access the sdcard in ./adb shell what do you see?
haxin said:
when you access the sdcard in ./adb shell what do you see?
Click to expand...
Click to collapse
The content of the internal sd card (`ls`), which is a single empty recovery dir atm. I need to recover the content (i.e. undelete).
Eventually I'm now dd-ing data from internal sd to a usb drive attached to dock USB. This way I can perform an ordinary data-recovery on the USB drive
What I did was:
- install a ROM with terminal emulator in it
- open terminal emulator (followed by the su command)
- dd with default blocksize (512) from interal to usb drive (after checking mounting points with mount command):
Code:
dd if=dev/block/mmcblk0p7 of=/dev/block/vold/8\:1
There is probably a more efficient way doing this (using ADB), but I'm finally able to recover the data, happy now
S3 internal SD card
I have an Samsun S3 with JB update. Now the internal SD card is no longer visible as USB drive from the PC. It cannot be done based on other threads.
Can I use the following method to get around the UMS issue? Can I use a Terminal Emulator app? can I dump to external SD card and then run recovery SW on it?
My phone is rooted and after su on TE, I can see /mnt with both sdcard and extsdcard mount points..
Tutti-frutti said:
Eventually I'm now dd-ing data from internal sd to a usb drive attached to dock USB. This way I can perform an ordinary data-recovery on the USB drive
What I did was:
- install a ROM with terminal emulator in it
- open terminal emulator (followed by the su command)
- dd with default blocksize (512) from interal to usb drive (after checking mounting points with mount command):
Code:
dd if=dev/block/mmcblk0p7 of=/dev/block/vold/8\:1
There is probably a more efficient way doing this (using ADB), but I'm finally able to recover the data, happy now
Click to expand...
Click to collapse
cell800 said:
I have an Samsun S3 with JB update. Now the internal SD card is no longer visible as USB drive from the PC. It cannot be done based on other threads.
Can I use the following method to get around the UMS issue? Can I use a Terminal Emulator app? can I dump to external SD card and then run recovery SW on it?
My phone is rooted and after su on TE, I can see /mnt with both sdcard and extsdcard mount points..
Click to expand...
Click to collapse
If you can see the mounting points, why not just try it?
In my case, it turned out that a lot of my data was already overwritten. I could recover some pictures and docs.
Hi. Beginner here, Please, how long this command will take to dumb about 29 GiB to a regular Micro SD card? I am waiting for minutes.
dd if=dev/block/mmcblk0p7 of=/dev/block/vold/8
Thanks.

Dosbox Turbo Help

I just installed Dosbox Turbo and it sees my Transformer TF700 internal storage as /sdcard/
I knew that was normal, but can't figure out how to mount my dock's sdcard.
I tried
"mount d /removable/sd" and got "Directory /removable/sd doesn't exist."
I also tried every other path I could think of. Does anybody have any insight that could help me?
I might just copy the game folders onto internal storage, but it bugs me that I can't get this reading the card.
By the way, I'm running stock JB 4.1.1, not rooted, not unlocked.
AnakiMana said:
can't figure out how to mount my dock's sdcard.
Click to expand...
Click to collapse
The tablet should mount it itself, and show an SD card icon at the bottom of your screen, if it is recognized.
What is the format of the card (FAT32, exFAT, NTFS, etc)? Using an unsupported format or unformatted card is usually the reason for it not to be recognized and mounted.
Total Commander shows all SD cards (and USB drives) at the top of it's main browse screen, including their path.
My MicroSD card is mounted as /Removable/MicroSD. Please note that Linux, thus Android is case sensitive. Meaning that upper and lowercase letters are not treated the same as in Windows for example. So /removable/sd is not the same as /Removable/SD.
If you are using Android Terminal Emulator, use the tab key to activate the auto complete feature. Type /R, then press tab and it will complete it if there is only one match (in this case /Removable/). When there is more than one match, it will show you a list of matches. This way it is easier to not make a typo when using long paths.
Thanks for your reply.
The card was always visible from File Manager (Asus app), I just hadn't been able to use the mount command successfully in Dosbox.
I got it working by using proper capitalization, as you suggested! Thanks!
The answer, for anyone else with this issue, is: /Removable/SD
So, the command from Dosbox is "mount d /Removable/SD", to make the sdcard your D:\ drive.

T-Mobile LG G5 SD Card (adoptive storage or regular SD) how to make it default

In the past on my Android phones, primarily LG, I have had SD cards installed and they became the default storage location for download, DCIM, images saved from any program, etc. Now I have the G5 and it seems to be quite different. I have an SD card installed and it seems there is no way to make it the default location as it has been in the past. I understand that adoptive storage can be made to work to use the SD card for more 'internal' RAM but I have had two issues with this, 1. I can't see the phone with ADB when connected to my PC and 2. I can't seem to find adoptive storage instructions that work. I am not new to LG or Android phone but this one has me a bit confused. Can adoptive storage be used on the T-Mobile G5 and/or can the SD card be made the default location for the G5 to store things, like DCIM, downloads, etc like all the LG phones in the past?
Thanks,
T.E
I was able to get adoptable storage going, discovered there's a typo in Paul O'Brien's article, once I fixed that I was set to jet. This is an edit from Paul's article here:
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.
2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.
3. Umount the sdcard before connecting it in debug mode to your pc.
4. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.
5. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).
6. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179,160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179,160 mixed 50'. Easy right?
7. This took almost no time at all for me.
8. Go to the sdcard in storage and move data to it. This will then merge the space on the card and the internal storage.
HTH.
Ok, first problem first. I have the SDK installed, debug mode on and phone connected. I can see the file system on the phone but ADB DEVICES returns nothing. Until I can get that resolve I can't even do the rest.
Can anyone tell me how to get the T-Mobile LG G5 to be recognized by ADB?
Resolved and I believe I have the adoptable storage working now.
If this is done with a somewhat slow SD card will it have a negative impact on the entire system?
btothec said:
If this is done with a somewhat slow SD card will it have a negative impact on the entire system?
Click to expand...
Click to collapse
Maybe. Please correct me if I'm wrong but adoptable storage tries to only put stuff on the sdcard that will live comfortably there. Nothing system related will go there, so worse case an app takes longer to launch.
scottricketts said:
Maybe. Please correct me if I'm wrong but adoptable storage tries to only put stuff on the sdcard that will live comfortably there. Nothing system related will go there, so worse case an app takes longer to launch.
Click to expand...
Click to collapse
I am using a 64gb Class 10 and have not noticed any significant change in performance.
scottricketts said:
I was able to get adoptable storage going, discovered there's a typo in Paul O'Brien's article, once I fixed that I was set to jet. This is an edit from Paul's article here:
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.
2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.
3. Umount the sdcard before connecting it in debug mode to your pc.
4. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.
5. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).
6. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179,160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179,160 mixed 50'. Easy right?
7. This took almost no time at all for me.
8. Go to the sdcard in storage and move data to it. This will then merge the space on the card and the internal storage.
HTH.
Click to expand...
Click to collapse
Can this be undone? What happens if you remove the sdcard? Is it still readable in a PC, so the files could be recovered if the phone died?
Click on the sdcard then select make portable storage. No clue what happens if you take it out other than some programs won't work.
kchannel9 said:
Can this be undone? What happens if you remove the sdcard? Is it still readable in a PC, so the files could be recovered if the phone died?
Click to expand...
Click to collapse
If it gets encrypted you won't be able to read it in a PC.
Sent from my LG-H830 using XDA-Developers mobile app
Can someone that had done it please post pics of how is it supposed to look like once you do the process, the reason I asked is bc under storage I can see the storage as one but in many google apps I only the the the 32gb of storage and no 211gb like on the storage settings. Thanks in advance
TheEditor said:
Ok, first problem first. I have the SDK installed, debug mode on and phone connected. I can see the file system on the phone but ADB DEVICES returns nothing. Until I can get that resolve I can't even do the rest.
Click to expand...
Click to collapse
How did you do it im having the same issue?!?!?!?!
TheEditor said:
Resolved and I believe I have the adoptable storage working now.
Click to expand...
Click to collapse
how did you fix the adb shell problem?!?!?!
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
i get this when i type in adb shell
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Dawid>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Users\Dawid>
what do i do? how do I fix this?
you guys have adoptable storage working? do you guys like it? Yay Or Nay? i have it working fully no problems just i havent formatted my sd card yet. wondering if its worth doing.

Categories

Resources