Database Users

SD card lost with message "Removed SD card" after update to cyanogenmod

Did not get any help in cyanogenmod thread, so creating a separate thread here.
I am in trouble. After I updated my ROM to cyanogenmod 3.6.7.2 (with his recovery image 1.3.1 and latest radio) I get a message saying: "Removed SD Card" in the notification and I am getting force closes in apps which access sd card.
Why did it remove my sd card? I have the following partition structure"
c (formatted fat32) 2GB - this is what used for upgrading the radio and rom.
83 (formatted ext4) 6GB
c (formatted fat32) 7GB
82 (mkswapped) whatever left off from 16GB card.
Is this structure causing the issues? I used Linux 2.6.30 and e2fsprogs 1.41.7 to format ext4 and dosfstools 3.0.2 to format fat32 FSs.
I ran fix_permissions from recovery console because I was getting FCs in powermanager (which logs files on SD card).
Also, if I boot into the recovery console, I can mount /sdcard and it automatically mounts the first fat32 partition on /sdcard. I can 'fdisk -l' and see all my partitions are there. So, its not a hardware issue. Some sort of chicken&egg because of apps2sd.
I just mounted the partition2 (which is ext4) in recovery console and I can see there are "app app-private dalvik-cache lost+found" folders on it. So, it looks like normally initialized.
Does anybody know what's going on here? Appreciate your help!

It's the same response you've been getting in the other section.
Try backing up your data on your computer, and completely formatting your card to fat32.
From there, instead of making the partitions on the computer, use the Recovery Console (accessed from Cyano's Recovery) and re-create the partitions as you like.

Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.

devsk said:
Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.
Click to expand...
Click to collapse
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?

akapoor said:
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?
Click to expand...
Click to collapse
Yeah, I just removed the 3rd and 4th partitions from recovery console and the card is recognized and working fine. Now, I need to find out why is it hard coded like that.

It seems like something doesn't like more than 3 partitions on the SD card. I now have 3 partitions with 'c' (fat32), '83' (ext4) and 'c' (fat32) codes and it seems to work fine.

An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP

B-man007 said:
An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP
Click to expand...
Click to collapse
I've heard this repeated elsewhere but nobody ever actually says what the problem is with partitions greater than 1.5gb. I'm very curious to know, because I haven't noticed anything wrong.
Except that /sdcard won't automount if my sd card has 4 partitions defined on it. As soon as I mark the 4th one empty and reboot, it's fine again. But that has nothing to do with the size of the ext fs on partition 2. Something with vold is funky, because I can mount /sdcard manually from adb.

[FIX] CM7: Fixes for SDCARD issues

Here are a some fixes that should help with some (most?) of those having
'sdcard' issues (or hoping to avoid them):
The first fix should be applied by everyone. It fixes the fsck_msdos
program. This program is used to check your 'sdcard' for errors before
using it. This program can also correct many of these errors. After
this fix is applied, you should see a notification after booting:
Preparing SD card
Checking for errors.
This notification will last until it is done checking. That will last
around 30 seconds (can vary greatly depending on size of 'sdcard' and
number of files on it, etc.). If this notifcation is replaced with
one that states 'Damaged SD Card', then the fsck_msdos was unable
to correct the errors. Hopefully, with this fix (barring some other
major incident), all of the minor errors on the 'sdcard' will get
fixed before they become major errors that it cannot fix.
The fsck_msdos fix: http://www.mediafire.com/?g52q4zr03c3z1gx
Apply with your favorite recovery software.
NOTE: The fsck_msdos fix should be applied before any of the other fixes.
Also, you should boot at least once after applying the fix to allow it to
check/fix the 'sdcard'.
The other fixes are not true fixes, but work-arounds for the 50+
apps on sdcard issue. One of them allows you to increase the size
of your 'Internal storage' so you do not have to move apps to the
'sdcard'. The other allows you to move these apps back to the
'Internal storage' after you have encountered the 50+ issue.
After the "Preparing SD card" notification goes away, after about
a minute (can vary), do you see the following notification:
Removed SD card
SD card removed. Insert a new one.
If so, that (most likely) means that you have encountered the
50+ issue. To fix it, you will need to move apps back from
the 'sdcard' to the 'Internal storage' (or 'phone').
The next fix/workaround allows you to 'stash' some of the apps
on the 'sdcard' so that the 50+ issue does not come into play.
This will allow you to move apps back from the 'sdcard' without
encountering the "Removed SD card" error while attempting to do so.
Each time you apply this 'fix', it will 'stash' all but 40 of
the apps on the 'sdcard'.
So, apply this fix once. Then move apps back from the 'sdcard' to
the 'phone' (or 'Internal storage'). Note that apps that have been
'stashed' might show with a greyed-out icon with an 'SD Card' symbol
and the letters 'SD' -- do not attempt to move these. After you
have moved the apps from the 'sdcard' back to 'phone' (those that
haven't been 'stashed'), you apply the fix again. Applying the
fix the second time will 'unstash' the remaining apps (remember
that it will not allow more than 40 apps to be 'unstashed') thus
allowing you to move them off the 'sdcard' too.
Get it here: http://www.mediafire.com/?4n3fhag1d33127q
Apply with your favorite recovery software.
The last fix/workaround allows you to increase the size of your
'Internal storage'. This will allow you to store more apps on
your 'Internal storage' and avoid having them on the 'sdcard'.
To check your current 'Internal storage' space, go to
Settings/Storage and note the values under 'Internal Space'.
If the size of the 'Available Space' is not enough to hold
all the apps you are moving back from the 'sdcard' (or apps
that you will install in the near future), you will need
to increase the size of your 'Internal Space'.
You can increase the size of your 'Internal space' (or /data)
in increments of 256MB, 512MB, 1024MB and 2048MB. You apply
these 'fixes' with recovery software (tested with CWM and TWRP),
however, please note the warnings below.
********** PLEASE READ ALL WARNINGS BELOW **********
********** PLEASE READ ALL WARNINGS BELOW **********
data_plus_256mb: http://www.mediafire.com/?gxqjki8s255lwpw
data_plus_512mb: http://www.mediafire.com/?wh83t6urhnf82ad
data_plus_1024mb: http://www.mediafire.com/?zaeh4fd3pjinaga
data_plus_2048mb: http://www.mediafire.com/?xyxdx7xscee6mex
********** PLEASE READ ALL WARNINGS BELOW **********
********** PLEASE READ ALL WARNINGS BELOW **********
WARNINGS:
1) BACKUPS. BACKUPS. BACKUPS. As always, and especially when you
are resizing filesystems, you should have backups. This means
backups of all data (that you would care about losing) on the
Touchpad. These backups should be stored off of the Touchpad.
2) Before attempting to resize your 'Internal space' make sure
you have enough free space on your 'sdcard' to do so. Check
this from Settings/Storage/SD card/Available Space. You should
have enough space plus a very healthy 'safety margin'.
DO NOT ATTEMPT TO TAKE ALL (OR CLOSE) AVAILABLE SPACE FROM SDCARD.
3) Before applying this 'fix', make sure you have plenty of charge
on your battery.
4) Do not reboot, reset or otherwise interrupt the touchpad while
applying this 'fix'.
5) As soon as this 'fix' is complete, use the recovery software's
reboot command to reboot the system. Do not do anything else
in recovery after applying this 'fix'. This 'fix' does things
that recovery software are not designed to do and does not
expect to happen. REBOOT IMMEDIATELY AFTER APPLYING FIX.

reserved ....................

reserved ..........

just got touchpad. i haven't encounter any issues with the sdcard yet. though i haven't installed too much yet. will keep eye on this. i like the tweaking of the partition sizes. seems easier than the webos doctor way.

thank you for your effort,
I was wondering if this can enable the USB host feature as well?
I have the Micro SD to female USB, which works fine with my galaxy S II phone but never with the touchpad. I saw youtube work arounds which are not very practical (using an external source of power)
thanks again

dundroid said:
thank you for your effort,
I was wondering if this can enable the USB host feature as well?
I have the Micro SD to female USB, which works fine with my galaxy S II phone but never with the touchpad. I saw youtube work arounds which are not very practical (using an external source of power)
thanks again
Click to expand...
Click to collapse
No, does nothing whatsoever related to USB host.

I have the 32gig unit and over 100apps. And have had zero issues with the SD card... Am i just a lucky guy? Why would we not all have the problems? Not complaining im glad i have no issues but it find it strange how we all run the same hardware and there are only 3 maybe 4 android roms that can be installed.
Is there any explanation as to why some and not others have SD issues?
Ill keep this thread in mind if i should ever encounter issues.

TKG26 said:
I have the 32gig unit and over 100apps. And have had zero issues with the SD card... Am i just a lucky guy? Why would we not all have the problems? Not complaining im glad i have no issues but it find it strange how we all run the same hardware and there are only 3 maybe 4 android roms that can be installed.
Is there any explanation as to why some and not others have SD issues?
Ill keep this thread in mind if i should ever encounter issues.
Click to expand...
Click to collapse
Note that the first fix (fsck_msdos) should really be applied by anyone as
it helps prevent minor errors on the 'sdcard' from becoming major errors.
For the 50+ apps issue, it is not the total number of apps installed, but
the number of apps installed to the 'sdcard'. Go to Settings, Applications,
Manage Applications, SD Card ... how many of those have a checkmark
in the boxes on the right?

I got a warning that I was low on internal space today so I ran the 3 fixes; fsck_msdos, stash apps, and then I ran the data plus 1024mb and received a checksum failure 4 after the script ran. I rebooted and the tablet still has 186mb free space. I downloaded the data plus 2048mb zip and ran it in recovery, on reboot I still have 186mb free space and my free space on the sd card went down by 2gb. I'm sure I did something wrong but any help would be great.

bilbo6209 said:
I got a warning that I was low on internal space today so I ran the 3 fixes; fsck_msdos, stash apps, and then I ran the data plus 1024mb and received a checksum failure 4 after the script ran. I rebooted and the tablet still has 186mb free space. I downloaded the data plus 2048mb zip and ran it in recovery, on reboot I still have 186mb free space and my free space on the sd card went down by 2gb. I'm sure I did something wrong but any help would be great.
Click to expand...
Click to collapse
I'm not aware of any error that says: "checksum failure 4"
When you ran the "data plus 2048mb", did it say "FAILED" or "SUCCEEDED"?
Please copy the full output from the "data plus" script that you get.
Also, are you 100% SURE that the size of the 'sd card' went down by 2gb?

jcsullins said:
I'm not aware of any error that says: "checksum failure 4"
When you ran the "data plus 2048mb", did it say "FAILED" or "SUCCEEDED"?
Please copy the full output from the "data plus" script that you get.
Also, are you 100% SURE that the size of the 'sd card' went down by 2gb?
Click to expand...
Click to collapse
OK I was wrong it wasn't checksum 4 it was fsck cm-data failed rc=4
here is the entire message
preparing tools...
Checking media...
Media 26136=> 24088 cm_data:1536=>35861
media_fs tot=26123 sz=10510 free=15613
checking cm-data...
fsck cm-data failed rc=4
> >failed <<
Yes the free space went from 17xxxmb to 15xxx mb
Bill

bilbo6209 said:
OK I was wrong it wasn't checksum 4 it was fsck cm-data failed rc=4
here is the entire message
preparing tools...
Checking media...
Media 26136=> 24088 cm_data:1536=>35861
media_fs tot=26123 sz=10510 free=15613
checking cm-data...
fsck cm-data failed rc=4
> >failed <<
Yes the free space went from 17xxxmb to 15xxx mb
Bill
Click to expand...
Click to collapse
Not sure why your free space went from 17xxxmb to 15xxxmb.
Based on the output you provided, the script made no changes.
If either the "Checking media" or "Checking cm-data" fail, it will
not make changes. This is by design. What else did you do between
the free space being 15xxxmb and 17xxxmb? Did you do a backup?
The "fsck cm-data failed rc=4" indicates that it finds uncorrectable
errors on the "/data" filesystem and it is refusing to do the resize.
Doing a "ACMEUninstall" and the re-installing should fix the errors on
the "/data" filesystem.

Is the fsck_msdos fix specific to the Touchpad or can it be run on other Android phones running CM7?

Prey521 said:
Is the fsck_msdos fix specific to the Touchpad or can it be run on other Android phones running CM7?
Click to expand...
Click to collapse
It is only for the Touchpad.

jcsullins said:
Not sure why your free space went from 17xxxmb to 15xxxmb.
Based on the output you provided, the script made no changes.
If either the "Checking media" or "Checking cm-data" fail, it will
not make changes. This is by design. What else did you do between
the free space being 15xxxmb and 17xxxmb? Did you do a backup?
The "fsck cm-data failed rc=4" indicates that it finds uncorrectable
errors on the "/data" filesystem and it is refusing to do the resize.
Doing a "ACMEUninstall" and the re-installing should fix the errors on
the "/data" filesystem.
Click to expand...
Click to collapse
damm mine did this also.. ok at least i know what to do.. thx

jcsullins said:
reserved ....................
Click to expand...
Click to collapse
Thanks for your usual great work.
1- will any of the 3 fixes/workarounds be included in alpha 3.6 so I can just wait for that? If so which ones?
2- The data image resizing will probably not be in 3.6 so if I resize to 2048 what, if any, data will I lose for sure?
I will do a Titanium back up pro of apps & data anyway & copy onto PC as you advised anyway. Thanks again for your work, much appreciated.

wozhere said:
Thanks for your usual great work.
1- will any of the 3 fixes/workarounds be included in alpha 3.6 so I can just wait for that? If so which ones?
2- The data image resizing will probably not be in 3.6 so if I resize to 2048 what, if any, data will I lose for sure?
I will do a Titanium back up pro of apps & data anyway & copy onto PC as you advised anyway. Thanks again for your work, much appreciated.
Click to expand...
Click to collapse
The fsck_msdos (sdcard check) fix should be in alpha 3.6. The resizing adds
that amount to what you already have. You typically will lose no data with
the resize if you heed all the warnings.

Thanks JC.

Hi JC,
Using the dataplus 2048 fix on my CM7 now for a couple of weeks and it's working great. Just looking ahead, do you know if this fix will also be applicable with the upcoming CM9? Thanks.
Mike T

I did install the 2GB partition zip file along with the fix file.after a reboot, the total internal space showed me something around 3.5GB, which i think is normal.
But the issue that i'm facing now, is that after installing around 30 apps, i'm not able to install any more apps. It shows me an error message saying that the app cannot be installed. I did try clearing the cache from recovery, but problem is still present. Internal space remaining is showing something around 1.5GB though.
Please help.
Thanks

A7+ memory and extrenal card issue

From elocity about A7+:
The 4GB internal high speed flash memory can store up to 4 feature films, 40,000 photos, or 2,000 songs for countless hours of entertainment. Wireless & Bluetooth.... BLA bla bla.
.................................
Ok, I have been searching and finding related information but confusing me more.
I have an A7+
it came with a 8 gb card, I can't figure out how to save to card, downloads, apps etc.
It never gives choice. No options in settings > memory card or when downloading
Besides the external card issue, and because of my novice tech knowledge I don't under stand what takes up space and best way to manage with A7+ or if different then A7
The 8 gb card shows 7.39 gb available and has not changed since installed, card was new so I never formated it.
*I now have 39.62mb available user space (that's not a lot, is it?) thats after 4 gb factory and all systems use, that left me with 1.53 gb to work with?? (edit, I deleted about a dozen apps and a bunch of music. Now available internal memory is LESS, 39.61mb what's going on)?
I have downloaded a bunch of apps, I don't fully understand how this effects memory, I have about 250 songs, no movies and just a dozen or so photos
I'm guessing its the apps
Thanks in advance...

reply
well, this is more of an android topic and not A7.
anyway, to move apps to a card go to Settings/Applications and on some apps that aren't protected you will have the option to move to card. many file managers have an app backup option and will also allow you to copy/paste to/from your memory card. try Astro, it's very popular and works well.
saving downloads is sometimes done by the settings of which ever program you are using. as far as i can tell the default browser and firefox mobile only save to onboard.

Astra was not available for the A7+ that I could find, I found Es explorer app and yet to find area for my needs in it, I guess I need more time on it, it looks like much more then I need and more complicated then I can manage
I just need a easy way to manage basic downloads like photos, music, apps

the device comes with a file manager preinstalled, i can't recall the name because my A7+ is not functioning and no one replied to my post.

I think 'OI manager' is the factory manager on my A7+.
With OI manager I tried to transfer files, apps (or anything) into my 8 GB card with no success, also tried 4 or 5 apps that advertise "app to SD" type ability along with more 'astro' type apps that claim to be file managers that should do what I need all with no luck, its like my device is locked to not to allow moving files
related issue, tablet was down to about 39.62MB internal space, after removing many apps and mp3s, it always seems to effect internal storage randomly, after clearing space I would sometimes loose available space, sometimes gain space, whats going on?? Is this a quirk with Android system?
The big one is, I decided to take the 16GB sd card out of my Blackberry and try in A7+. after first installing card everything was fine, all 200 or so photos and some videos from BB card showed up as expected (with device showing the majority of the 16GB sd card available) ....I went on to do something else and left the A7+ to go into stand by, when I woke it up, it says 'sd card is full please clear space' I go check available space and it is 0 and I can no longer access any pics, internal or on the 16GB card ?? I swap back the empty 8 GB card and show a total available internal 4.33MB and system seems to work ok except low memory storage. Note, that I had 39.62MB internal user space one week ago then up to ~60.14MB as of 24 hrs ago after a lot of cleaning of music and apps, then installed & removed other BB sd card and now down to 4.33MB. Its like Android Alzheimers or something as I now have very little memory space available and a device that does erratic things.
*Last thing, could it be the music I downloaded directly into device is corrupt or not compressed correctly or just to many files "or something I don't understand"? (the mp3s are in the internal 4GB storage that really is 1.53GB usable)
I still have about 200 songs downloaded from app called "MP3 Music Download" that I got from one of the included app stores, apk or Getjar??
Anyway to transfer those mp3s to pc or thumb drive then delete them from device and check status
I have emails into eLocity now for a couple weeks with no response from previously helpful contact
~eLocity A7+ with no mods, factory settings~

over's tab said:
I think 'OI manager' is the factory manager on my A7+.
With OI manager I tried to transfer files, apps (or anything) into my 8 GB card with no success, also tried 4 or 5 apps that advertise "app to SD" type ability along with more 'astro' type apps that claim to be file managers that should do what I need all with no luck, its like my device is locked to not to allow moving files
related issue, tablet was down to about 39.62MB internal space, after removing many apps and mp3s, it always seems to effect internal storage randomly, after clearing space I would sometimes loose available space, sometimes gain space, whats going on?? Is this a quirk with Android system?
The big one is, I decided to take the 16GB sd card out of my Blackberry and try in A7+. after first installing card everything was fine, all 200 or so photos and some videos from BB card showed up as expected (with device showing the majority of the 16GB sd card available) ....I went on to do something else and left the A7+ to go into stand by, when I woke it up, it says 'sd card is full please clear space' I go check available space and it is 0 and I can no longer access any pics, internal or on the 16GB card ?? I swap back the empty 8 GB card and show a total available internal 4.33MB and system seems to work ok except low memory storage. Note, that I had 39.62MB internal user space one week ago then up to ~60.14MB as of 24 hrs ago after a lot of cleaning of music and apps, then installed & removed other BB sd card and now down to 4.33MB. Its like Android Alzheimers or something as I now have very little memory space available and a device that does erratic things.
*Last thing, could it be the music I downloaded directly into device is corrupt or not compressed correctly or just to many files "or something I don't understand"? (the mp3s are in the internal 4GB storage that really is 1.53GB usable)
I still have about 200 songs downloaded from app called "MP3 Music Download" that I got from one of the included app stores, apk or Getjar??
Anyway to transfer those mp3s to pc or thumb drive then delete them from device and check status
I have emails into eLocity now for a couple weeks with no response from previously helpful contact
~eLocity A7+ with no mods, factory settings~
Click to expand...
Click to collapse
I also have the same problem customer support was trying to help me but all I succeeded in doing was move an ebook to files and now I can't get it back or read it. I have never formatted my 8 gb card so I don't know if that is the step I missed. My stepdaughter printed out the manual but unfortunately it is more an overview than a step by step. It IS in the oi file manager. I also noted that when I tried to move the book that there was a thin strip that said move file and maybe that sucked me into loading the book to my files. My A7 also played youtube videos at first but now it don't. It will play other sites but if they go to youtube it comes and attacks the site. youtube has declared war on me and I don't know why or how to make them stop. bye for now frank

Thanks for input on this. I was never able to get issues resolved, the return period was almost up so I decided to return it 'no questions asked'
To many things building against it, lacking support online and from manufacturer, I will miss many aspects of the A7+, a nice little tablet with potential, but.....
I now have an Archos 80 G9 (8" 3.2 Honeycomb w/ 8GB) it also packs a lot for the money, so far so good
Edit: forgot to mention, on eLocity the 'HOME' key had stopped working completely

Dropped the ball
No matter what you do you cannot get the Elocity A7 or A7+ to load to the SD card.....we have been trying for months and no matter what we do nothing works. The damned thing has so much potential and is suck a powerful little machine that it is a shame that the bloody company dropped the ball. We did manage to to get it onto every market in the world and we changed the 4 Gig internal to a 32 Gig internal and reloaded the Titanium backup onto the card with the PC so there is more space and now the SD is primarily storage and a media file. To think that all they had to do was try a little harder and this would have been a monster in the market place last year. Oh well, maybe someone else will create a tablet that is fun and easy to use.

blooknight154 said:
No matter what you do you cannot get the Elocity A7 or A7+ to load to the SD card.....we have been trying for months and no matter what we do nothing works. The damned thing has so much potential and is suck a powerful little machine that it is a shame that the bloody company dropped the ball. We did manage to to get it onto every market in the world and we changed the 4 Gig internal to a 32 Gig internal and reloaded the Titanium backup onto the card with the PC so there is more space and now the SD is primarily storage and a media file. To think that all they had to do was try a little harder and this would have been a monster in the market place last year. Oh well, maybe someone else will create a tablet that is fun and easy to use.
Click to expand...
Click to collapse
i fixed the kernel in my A7CompPlus release, and apps can be installed on sdcard, and i think i updated it in the Cyanogen release as well.
it just took some kernel recompile and different framework, since elocity framework does not support this at all (it is removed from the firmware completely).
so you cannot get the feature unless you try a custom rom.

Dexter_nlb said:
i fixed the kernel in my A7CompPlus release, and apps can be installed on sdcard, and i think i updated it in the Cyanogen release as well.
it just took some kernel recompile and different framework, since elocity framework does not support this at all (it is removed from the firmware completely).
so you cannot get the feature unless you try a custom rom.
Click to expand...
Click to collapse
Dexter, Thank You for your work on A7+. I am enjoying your CM7 rom but can't get apps to load to SD. Tried every combination of settings. Are there any performance disadvantages to modding vold.fstab file ot make the SD card internal? Also please give update on your ICS mod work. I appreciate any suggestions.

denmichelson said:
Dexter, Thank You for your work on A7+. I am enjoying your CM7 rom but can't get apps to load to SD. Tried every combination of settings. Are there any performance disadvantages to modding vold.fstab file ot make the SD card internal? Also please give update on your ICS mod work. I appreciate any suggestions.
Click to expand...
Click to collapse
i believe that external sdcard should work. but maybe its just found on the /mnt/sdcard location or what vold.fstab says?
have you checked its mounted? i am sure it should have worked. let me see if i get a chance to confirm or check.

Dexter_nlb said:
i believe that external sdcard should work. but maybe its just found on the /mnt/sdcard location or what vold.fstab says?
have you checked its mounted? i am sure it should have worked. let me see if i get a chance to confirm or check.
Click to expand...
Click to collapse
Thanks for your quick reply. I checked and SD is mounted and shows up in storage. I found the following generic vold.fstab which is supposed to be set up to make the external SD act as internal storage. Please comment on any changes that might be needed.
# Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# sdcard mount for the P1
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
discard = disable
asec = disable
}
#dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/msm_sdcc.4/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
#end line ## keep this line

denmichelson said:
Thanks for your quick reply. I checked and SD is mounted and shows up in storage. I found the following generic vold.fstab which is supposed to be set up to make the external SD act as internal storage. Please comment on any changes that might be needed.
# Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# sdcard mount for the P1
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
discard = disable
asec = disable
}
#dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/msm_sdcc.4/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
#end line ## keep this line
Click to expand...
Click to collapse
The file above did not work. The CM7 vold is below. Do you know what commands need to be changed to make the external card the primary internal storage.
# Vold 2.0 Malata Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci

you cannot make sdcard primary internal this happens in boot stage.
you can only switch internal storage card with external card.
just change the 2 first thing in 2 first lines /mnt/sdcard and /mnt/emmc and its done

Dexter_nlb said:
you cannot make sdcard primary internal this happens in boot stage.
you can only switch internal storage card with external card.
just change the 2 first thing in 2 first lines /mnt/sdcard and /mnt/emmc and its done
Click to expand...
Click to collapse
So it should now look like this. I tried it but storage seems same with external SD card showing my 8gb of storage and internal is still 1gb. Any other steps. Thanks for your patience. I really want to get more app storage.
dev_mount sdcard /mnt/emmc 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/sdcard 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci

denmichelson said:
So it should now look like this. I tried it but storage seems same with external SD card showing my 8gb of storage and internal is still 1gb. Any other steps. Thanks for your patience. I really want to get more app storage.
dev_mount sdcard /mnt/emmc 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/sdcard 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Click to expand...
Click to collapse
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
this is the correct way

Dexter_nlb said:
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
this is the correct way
Click to expand...
Click to collapse
Dexter, thanks for your continued help. I made the changes and everything looks and acts the same.Internal storage is 1g and external storage on Sd Card is 7.39 as it was before. My file card needed to be reformated before it was recognized. I rebooted after the changes anything else required?

denmichelson said:
Dexter, thanks for your continued help. I made the changes and everything looks and acts the same.Internal storage is 1g and external storage on Sd Card is 7.39 as it was before. My file card needed to be reformated before it was recognized. I rebooted after the changes anything else required?
Click to expand...
Click to collapse
i might actually have misunderstood, if i recall the A7 correct, internal storage is actually the /data partition that you cannot change, thats alot bigger process to fix.
you can only keep sdcard at the /mnt/sdcard location , the /mnt/emmc location was for USB connected devices in the CM rom.

Dexter_nlb said:
i might actually have misunderstood, if i recall the A7 correct, internal storage is actually the /data partition that you cannot change, thats alot bigger process to fix.
you can only keep sdcard at the /mnt/sdcard location , the /mnt/emmc location was for USB connected devices in the CM rom.
Click to expand...
Click to collapse
Dexter, I appreciate your timely responses and ongoing support for the A7+

[How To] Swap the mounting points on ICS (CM9) for emmc and sdcard.

This is a quick tutorial I want to write up based on a recent experience I've had recently with my micro sd-card. (More info on that below)
This how to shows how to switch between the internal sd card and the external sd cards mounting points (so the external is accessed via /sdcard, and the internal is accessed through /eemc)
The nuts and bolts how to:
0. Perform backups on System, i am not responsible for any damages or boot loops.
1. Download root explorer (or any other file explorer with root privileges)
2. Go to /system/etc, and mount R/W
3. Long press on vold.fstab and select Open With... , select Text Editor
4. You will find a line with sdcard in it a few times, change this section:
dev_mount sdcard /mnt/sdcard
Click to expand...
Click to collapse
To:
dev_mount emmc /mnt/emmc
Click to expand...
Click to collapse
5. Do the same thing with the emmc section:
dev_mount emmc /mnt/emmc
Click to expand...
Click to collapse
To:
dev_mount sdcard /mnt/sdcard
Click to expand...
Click to collapse
6. But you just flipped the first section around? Yes I did, this changes the mounting points. But not the original location of where it is being mounted......
7. Please don't change anything else in this file....
8. Reboot, enjoy!
I had to do this hax because the current nightly of CM9 doesn't support there being no external sd card, and mine got corrupt (eep!), it then continued to mount the internal sd card location to emmc instead (wtf?). So i did this quick hax so i could take pictures with the stock camera and use several applications which just default to the internal sdcard (and doesn't allow changing that).
Hope that helps some random Googlers......
Note: This has only been tested on CM9 Nightly apr-9th on SGSII, but i see no reason for this not work across all ROMs and devices( with ICS, the emmc thing wasn't on GB and below i don't think) as long as you don't do anything as foolish as change more than the lines specified above.
An example of a swapped file is (DO NOT COPY AND PASTE THIS, YOU PROBABLY WONT BE ABLE TO BOOT):
# internal sdcard
dev_mount emmc /mnt/emmc 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
Click to expand...
Click to collapse
Please note that the latest CM9 nightlies lets you do this from the system menu! This was written pre that advancement. This is for the curious and other ROMs/phones.

Is it possible to use something in the lines of:
dev_mount emmc /mnt/external_sd ? To just bind the external sd to the stock location?

If I understood your question right, that's the default behavior in CM7/9 so you don't need to change anything.
(internal gets mounted as /sdcard and external as /emmc. At least that's how it always behaved on my device -takes a bit of getting used to but it's manageable once you know the trick)
edit : aw sawry, mistook /mnt/external_sd for /mnt/sdcard. But it changes nothing besides the name of the mountpoint, easily adjustable.. Although why you would want to have it named like that is beyond me, it makes for more keys to hit when typing it... xD

Zewsan said:
Is it possible to use something in the lines of:
dev_mount emmc /mnt/external_sd ? To just bind the external sd to the stock location?
Click to expand...
Click to collapse
same doubt raised here ...is it possible to mount external sdcard to /mnt/external_sd instead of mnt/emmc...???
please need solution

Zewsan said:
Is it possible to use something in the lines of:
dev_mount emmc /mnt/external_sd ? To just bind the external sd to the stock location?
Click to expand...
Click to collapse
Its the same technique....
So remember this:
Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
Click to expand...
Click to collapse
So <label> doesn't really matter, but we may as well keep it sane (and have it the same name as the mount point)! And <mount_point> is where its mounted. Make sure the folder exists first though! leave <part> and <sysfs_path*> alone and it will work correctly.
So if you were to create a folder /mnt/hammertime , then make a line look something like this (taken from my example in first post)
dev_mount hammertime /mnt/hammertime auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
Click to expand...
Click to collapse
That will work correctly.
Hope that helps!

mattisdada said:
Its the same technique....
So remember this:
So <label> doesn't really matter, but we may as well keep it sane (and have it the same name as the mount point)! And <mount_point> is where its mounted. Make sure the folder exists first though! leave <part> and <sysfs_path*> alone and it will work correctly.
So if you were to create a folder /mnt/hammertime , then make a line look something like this (taken from my example in first post)
That will work correctly.
Hope that helps!
Click to expand...
Click to collapse
is there no any requirement of changing build.prop file after doing this....?????

Ok I'll bite, late night tonight I'm going to flash back to AOKP....and give it a shot. It can't be that simple.....
Most certainly appreciate your effort...been looking for this for some time now.l!

HAvoktek said:
Ok I'll bite, late night tonight I'm going to flash back to AOKP....and give it a shot. It can't be that simple.....
Most certainly appreciate your effort...been looking for this for some time now.l!
Click to expand...
Click to collapse
I didn't think so either, but i had the problem, hoped it was like its Linux cousin and searched for fstab, i found it. Swapped the mounting destinations around. And voila, done.....

Swapped but CWM Recovery still the same
Hi, first of all nice guide you did here.
Here's the thing: somehow somewhere by flashing nightlies i ended up
with /sdcard being treated as my external SD while /emmc was for internal.
So I wanted to fix that and using your guide although the other way around
I was able to make it as such: /sdcard = internal storage; /emmc = external storage.
ALL IS GOOD however when i booted to CWM recovery:
CWM still mounts my internal storage as /emmc.
SO in recovery internal storage = /emmc while when in CM9 internal storage = /sdcard
Is there anyway i can change CWM so that internal storage = /sdcard? to be more uniform and not confusing

jeromepaez said:
Hi, first of all nice guide you did here.
Here's the thing: somehow somewhere by flashing nightlies i ended up
with /sdcard being treated as my external SD while /emmc was for internal.
So I wanted to fix that and using your guide although the other way around
I was able to make it as such: /sdcard = internal storage; /emmc = external storage.
ALL IS GOOD however when i booted to CWM recovery:
CWM still mounts my internal storage as /emmc.
SO in recovery internal storage = /emmc while when in CM9 internal storage = /sdcard
Is there anyway i can change CWM so that internal storage = /sdcard? to be more uniform and not confusing
Click to expand...
Click to collapse
Yeah CWM doesn't read the /system stuff, it has its own partition....
I've got no idea sorry, but its just a little inconvenient in CWM thats all.... But im sure you can check it out... Just search for fstab when you figure out how to explore the recovery partition (I've got no idea , short of modifying a flashable zip first and rekeying it.)

Forgot to post back with my results, Got HFS & AOKP to see the changes, however something broke when I did a PC mount. After playing with the lines "Experimentation" if you will, I ended up needing to rebuild my partitions! No fault of yours, I just wanted to see if I can have that functionality through the whole phones usage and features eg. mounting to the PC.
Thanks for the guide though, I'm seeing now that some devs are including the option to use the internal memory via a menu select, I wonder how there implementing that.

Probably something very similar but programmatically instead of the haxy file editing method I'm noting to use .
PC mounting is working as per normal for me here though...... (I don't have an external card right now so that may be a variable)

mattisdada said:
Probably something very similar but programmatically instead of the haxy file editing method I'm noting to use .
PC mounting is working as per normal for me here though...... (I don't have an external card right now so that may be a variable)
Click to expand...
Click to collapse
That it is, cause I can see my internal, but it doesn't mount the external.

Purpose
What is the purpose of this? Does it mount the EMMC so that the system thinks EMMC is actually an external sd card?
I am trying to figure out if there is a way to make the above mentioned happen. Or is there a way to re-partition it so that EMMC is used as system memory... or maybe even both? It seems that since ICS better integrates with on board memory, there would be a way to better integrate the internal memory of older devices with the system.

hfj00788 said:
What is the purpose of this? Does it mount the EMMC so that the system thinks EMMC is actually an external sd card?
I am trying to figure out if there is a way to make the above mentioned happen. Or is there a way to re-partition it so that EMMC is used as system memory... or maybe even both? It seems that since ICS better integrates with on board memory, there would be a way to better integrate the internal memory of older devices with the system.
Click to expand...
Click to collapse
This guide shows you how to "flip" the points. Several ROMs have it differently preconfigured. But if this is your current situation:
Code:
Emmc: External SD Card
SDcard: Internal SD Card
It will make it:
Code:
Emmc: Internal SD Card
SDcard: External SD Card
And vice versa obviously (its a flip).
This guide will do what your wishing it to do.
The folders sdcard and emmc (or there /mnt varient more closely) are just soft links, meaning they don't really exist, but just point to another location. We can modify which folder they are linked to in the fstab.void file.

so to make emmc to external_sd i change "dev_mount emmc /mnt/external_sd"?

Worked great on a Captivate running AOKP-36 right after a wipe data/factory.

lol you need no guide on cm9
you can switch them in storage settings by a simple checkbox
its mentioned in team hacksung's FAQ

Im on CM9. Can someone post the code so i can just do a simple copy and paste? I wanna switch emmc to external_sd
(there is no storage settings simple checkbox for me)
Sent from my SGH-I997 using xda premium

bradman117 said:
Im on CM9. Can someone post the code so i can just do a simple copy and paste? I wanna switch emmc to external_sd
(there is no storage settings simple checkbox for me)
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Never use a copy and paste for the file in this operation. You only need to modify partially two lines (which you can copy and paste from the OP).
Your just swapping two words around really. Its fairly easy, just follow the steps and it will work, it looks daunting at first if your not used to doing this sort of thing, but its fairly easy.

Ext4 / NTFS MicroSd & Usb Mounting -v2.3 (fat32 UMS) MTP/UMS Switching/ CM9/10 info

Ext4 / NTFS MicroSd & Usb Mounting -v2.3 (fat32 UMS) MTP/UMS Switching/ CM9/10 info
Hi,
i have developed an App, EzyMount - that pretty much takes care of mounting & utilising ext4 / ntfs storage properly. So no need to be limited to 4gb file size restrictions anymore !!
Updated info for CM9 / CM10 builds
****************************************************************
It seems that CM9 /CM10 changes the default mount point for external sdcards
For ntfs partition only sdcard
Change the default mount point to: /storage/sdcard1
Then try mounting here it should work ok and be picked up automatically by other Apps as well.
If you have two partitions:
1st Partition would be vfat then this should get auto mounted to /storage/sdcard1
2nd Partition (ntfs) : change the mount point to: /storage/sdcard0/extStorages1
Then try mounting here it should be ok
*****************************************************************
Version 2.3 Update
Universal Mass Storage Mode support for 7.7 tabs also most other devices.
Auto MTP/UMS Switching
When you select either MTP Mode or UMS Mode, the App will automatically switch your device into these respective USB transfer method.
It is also possible to use UMS mode for any external MicroSd card, fat32, Ext4 or NTFS formatted.
For ext4 / ntfs this is taken care of by the App
For fat32 external sd cards (these are mounted automatically by Android)
Create a new Mount Point which is the folder location of your external MicroSd card.
For example, on Galaxy 7.7 devices - this will be /mnt/sdcard/extStorages/SdCard.
For Galaxy S3 devices - this will be /mnt/extSdCard
For other devices this is typically, /mnt/sdcard/external_sd
In the partition setting put: /dev/block/mmcblk1p1
Once you have created this mount point, just select "UMS Mode".
After you have finished copying files to or from your PC, it is important to "safely eject your usb device from your PC".
Important too - Finally, disable "UMS Mode" by it pressing again.
You can switch back to MTP by selcting "MTP Mode".
(If MTP does not become active straight away (Android being slow too pick up the change)- you may need to Go to : Settings > Storage > USB PC connection & toggle between Media Device (MTP) & Camera PTP. So Android re-starts MTP. However, it should work without this step)
*****************************************************************
Version 2.1 update
1) New Sliding UI.
2) Ability to mount up to 10 devices / partitions.
Just create a new Mount Point for each device / partition you need to mount.
To create a new Mount Point:
Just slide the UI to the "mount another drive or partition". Then just use select a mount option as per usual to create a new mount point and mount at the same time. Or you can press the "microsd info" "usb drive info" to create a new Mount Point.
3) Works with ICS update
Just ignore "ICS warning messages" - when it comes to ntfs usb devices.
*****************************************************************
Version 1.7 update
1) Quite a few new features added:
NTFS / Ext4 MTP Modes - this allows you to easily switch between "normal mode" and MTP mode.
MTP mode is used for transferring files to PC.
Usage Example:
Personally, I have a 32 gb sd card
the First partion on it is an exFat 4 gb partition. This is picked up the tab and mounted as normal to the location of /mnt/sdcard/extStorages/SdCard
I can use this for my cwm backups etc, other files etc - system running as normal.
This 4gb partition will show up in windows via MTP.
The problem:
I also have a 28GB Ext4 second partition on the Card , this could be an NTFS partition too.
I want this too show up in windows so I can transfer (br rips etc) but it wont as the my first fat32 partiion is shown up instead.
By using NTFS MTP Mode or Ext4 MTP Mode - the App will automatically "switch" the partitions so the larger NTFS or EXT4 mode shows up in windows.
Once done then you can disable NTFS / EXT4 MTP MODE and the device will go back to normal as it were.
(the MTP folder location is set to work already for 7.7 devices and similiar. For other devices this needs to be adjusted. It is normally the default folder loaction of where the external SD card is mounted by the phone.)
UMS Mode - universal mass storage mode.
Although the 7.7 does not have ums mode (MTP is being standardised on ics devices and above) but there a lot of devices than can only use ums mode for transferring file to PC.
I have added a ums mode. Which basically makes your micro sd partitions available on pc. (suitable for non MTP devices)
You do not need to "turn on usb mass storage mode" just select "ums mode" from the APP and it will do it for you.
Also - in windows ext4 partitions are not recognised but ntfs one are off course. In linux both should be available. (one of the benefits of MTP)
Comaptibility Mode
Is for those users whose mounting of micro sd cards might fail for some reason. This mode tries a bit more thorough to mount your micro sd drives.
Better Error Messages
I have added a lot of better error messages that the de facto "error mounting " message
It should provide the reason why things might not be mounting.
I hope this helps some with issues and pm if you have any other issues or things you think might be useful to add.
( I will get round to updating the website with the added features soon)
*****************************************************************
version update 1.6
1) Fixed slight issue with Auto Ext4 permission handling.
2) Also changed the default mount folders of NTFS or Ext4 microsd card to the /sdcard/extStorages/SdCard
This should mean now MTP will see the card in windows properly and you can access them as you would normally. (I think this has caused some confusion - i had left this generic for other users on different devices)
(This means for other devices you should specify the folder in the "location" settings which is normally seen by windows MTP - i.e when you use a fat32 microsd)
I hope this has resolved some issues people might have been having.
version update 1.5
1) Modified labelling on some settings to make it clearer.
2) Mounting usb devices has been slightly tweaked to care of multiple partitions.
version update 1.4
Following on from your recommendations.
1) Mounting MicroSd Ext4 or Ntfs now automatically takes care of you partitions so you do not need to specify them.
This should make it much simpler to mount your microsd cards.
2) Usb Mounting widget should be compatible for all home screen launchers. (touchwiz, adwlauncher etc.)
************************************************************************************************************************************************************************************************************
please remember to unmount usb / microsd devices before ejecting - For usb devices you use the 1-click usb mount/umnount home screen widget for this or from within the App
************************************************************************************************************************************************************************************************************
There have been a few issues regarding using external Usb formatted Ntfs or Ntfs microsd drives. Also I wanted to use an internal micro sd Ext4 partition for large movies (1080p hi-def/bluray etc) or just keep them on an external Ext4 usb disk. Having looked at other solutions, there didn't seem like one that just "worked" or the way I wanted it to do so.
Using Ext4 over Ntfs is native to linux/android and it consumes less cpu than using ntfs. But you cant simply mount an ext4 device and start using it like a regular file system as the file permission are not properly created by Android. I also still needed to have Ntfs read/write support on occassions.
You can use any cheap otg usb cable found on ebay etc. (The same cables as used for 10" galaxy tab devices for example).
As I used the 7.7 as one of my development device so it is pretty suited for our tabs & similiar tablets i.e 7.0+ etc, but is more than generic enough to work on other devices.
The App provides all the necessary features and customization options so you don't need to worry about file formats, file size limitations or file permissions again !!
There are more tips on how to best use the app on my website. If you have any comments good or bad please let me know so I can improve the App.
Cheers.

Need help in mounting microSD as Mass Storage
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?

Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.

Asad_Khan said:
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?
Click to expand...
Click to collapse
belyj said:
Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.
Click to expand...
Click to collapse
Hi guys,
The default partition of your microsd card is typically:
/dev/block/mmcblk1p1
1) If you have only one partition - so you will put the following in the partition setting:
So for example an NTFS only formated microsd card :
/dev/block/mmcblk1p1
And the same would go for an Ext4 formatted only card:
/dev/block/mmcblk1p1
2) If you have two partitions then typically you will have:
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
And so on ..
(you can always check for these from a terminal/adb shell)
As these partitions are same for your microsd, you can set them once and forget them about afterwards. I don't try automatically choose these partitions for you and this depends on your partitioning scheme more than anything.
For Usb devices the App will automatically try mounting your usb partitions as these are likely to change more often then not.
Typically, I would recommend the following:
If you have a large 32gb / 64 gb microsd card
Create The first partition as fat32 - maybe 4gb.
This partition will be /dev/block/mmcblk1p1
The tab will automatically mount this first partition & you can use things like cwm recovery for backup as normal.
(Also you wont see an unsupported file system icon in your status bar.)
Then create a second large partition (ext4 or ntfs) :
This partition will be /dev/block/mmcblk1p2
So set this as your Ntfs partition or ext4 partition.
Once you can mount you microsd ok - then you can set it to automount boot.
So need to mess with the settings after that.
Hope this helps and please let me know.
Cheers.

Still MTP connection
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard

Asad_Khan said:
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard
Click to expand...
Click to collapse
I just tried this. If you click on the "portable device" in windows it shows up as tablet. You can copy files to where you mounted the sd card.
It should work fine.
For me I leave set pretty much as default. As I have the first partition on my sdcard as an exfat / fat32. Then I have an ext4 or Ntfs Partition. This way you tab will behave exactly as normal. But The App should be fine regardless of whatever partitions you have.
Please try this and let me know.
(Also I will look to be adding an auto mounting microsd feature in the next few updates if there is some demand for this. Plus any other features people might suggest in the meanwhile )
Cheers.

To those who have installed EzyMount,
I have updated the microsd mounting feature so it should automatically mount the correct partition for you.
You dont have to manually change the partition settings anymore.
Having said that if there is a particular partition on your microsd you want to mount, then put that in the settings. The app will first try to mount that partition, then try to mount the other partitions if the first mount was not successful.
Also i would suggest setting the mount point folder (location option in settings) to /sdcard/SOME_FOLDER
& not /ext/extStorages/SdCard. which is where the tab mount would mount the microsd card.
Let me know how it goes with the update.
Hope this helps.
cheers.

Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!

G8351427 said:
Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!
Click to expand...
Click to collapse
Hi,
I have slightly updated the labelling in the App so should a bit less confusing
You shouldn't really need to change anything.
Partition - refers to the actual "physical" location of your drive as sen by the Androis OS / kernel but this is taken care of automatically so you dont need to specify this. Although you can still specify a partition and that will be mounted.
(You can see the list of your partitions by doing ls /dev/block/* for a command prompt for example)
Location - is where your microsd or usb device will be mounted. Basically the folder loaction on your device where you can see its files / folder contents etc.
The other option refer to the various features - such as auto mounting at boot, auto fixing ext4 permissions, auto usb mounting. If you dont need them you can disable them.
So hopefully we can narrow down the issue.
Do you have busybox,superuser installed ok?
I am not sure what the actual "Usb Storage" on the note is. Maybe there is a variation in the labelling but it should be resolvable.
If you can get me the output from your device from an adb shell or connectbot for example of the following commands:
# mount
and
# df -h
These should help me figure out what might be going on.
(i'll see If i can get my hands on a galaxy note - or have a look at some of the dev stuff in the meanwhile)
Cheers.

Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.

-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
No problems - been busy with some other work.
So far the App has been installed on the note more tham any other device so seems to be working for some.
A lot of problems are being caused by some users not unmounting the usb device after mounting it for the first time. Which confuses things. I will be releasing an update that takes care of this and possibly a self diagnostics checker that should help in identifying some potential problems.
Also android / linux can be somewhat particular about ntfs so best run a drive check in windows first. Or even better can you try another newly formatted ntfs usb device and see if that works.
I will pm you once i get the chance.
Thanks.

-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
I have sent you a pm. Also i have been looking at some of the note dev threads so should have a solution for you I think.
Cheers.

Hi All,
Updated the App to version 1.7.
Check the first post.
Cheers.

This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.

rEVOLVE said:
This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.
Click to expand...
Click to collapse
You could use the solution ezynow mentions in the first post. Create a small fat32 partition at the start of the SD card, this will also be accessible by things like recovery. Then use the rest of the card as NTFS.

I should apologize for not seeing that tip in the OP. I'll have to wait till i've got some time to repartition the card - any suggestions of what size to make the small one?
Only other problem I see is that the "mount at boot" option doesn't seem to work and I still have to go to the app to enable this.

Trouble with Ext4 MTP
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
Thanks

GalaxyQuest99 said:
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
J
Thanks
Click to expand...
Click to collapse
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.

Diagnostic?
ezynow said:
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.
Click to expand...
Click to collapse
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks

GalaxyQuest99 said:
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks
Click to expand...
Click to collapse
Hi,
There should be a report generated under /sdcard/ezymount_test.txt.
Could you email it to [email protected].
If there isnt a report then email me at this address too so i can you send you an updated version of the app if needed.
Will setup ubuntu and test this also.
Cheers.