yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lordazoroth:
Sounds bad, I don't know why all these companies are sticking with Fat32 after all these years. Fat32 has been obsolete since like 2000, don't we have open source formats like ext4 now? - that's my rant lol. Either way, it works and I got the file. Btw, this file acts strangely on my device, I couldn't see it in windows explorer during plugin and It wouldn't copy to my sd card even though other files seem to be copying fine. Had to email it to myself from my phone. Thank you so much for all your help, let me know if you need anything else :)

Rename the file and remove .rar extension before use, xda doesn't allow .bin extensions to be uploaded.

Quick question: If I shut the phone down and pull the SD, can I turn the phone back on and use it without the SD while I load the SD up with files, then power off, re-insert the SD and power on again? (like will it automount again?)
[Verizon Samsung Galaxy S III] alquimista:
Yay!

Very interesting. I can go on the hunt for headers if you like. I have loads of sd cards.

Oddly enough, I switched to FAT32 even though I'm on a TouchWiz ROM, cause exFAT does not use alternating file allocation tables. When exFAT gets borked, it gets super borked and you have to use chkdsk (or some other brutish method) to retrieve files. When FAT32 gets borked, you can load the last table that was working and elegantly pull your files off the card (no need to muddle through a pile of chkdsk files and find the correct extensions).

Any possibility that this method could be used to mount a more robust file system like ext[2,3,4]? Journaling would be nice. Or some transaction safe file system.

Ta very much,

ALQI
[Verizon Samsung Galaxy S III] miyu-hitori:
Re: [MOD] Flashable exFAT support for CM10.1 / AOSP roms (external SD)

Great.I'll try it.
[Verizon Samsung Galaxy S III] lordazoroth:
Nice post lol, I only meant why FAT32 of all choices, these companies must know we're gonna be packing large files at some point, why knee cap us at 4gb when so many formats don't? Universal would be nice but of course it's entirely impractical :P

Thanks for the media scan info, that'll help a lot, I'll try out your suggestions tonight :D

Will do, sounds interesting, will there be data loss or just header corruption? second idea in mind?

Also, each time I take the card out of my phone (properly after shutdown of phone) and place it in my computer (vista 64bit ultimate) It asks to check for errors, i'll click continue (confirmation to check), takes 3-5 seconds, finishes with no errors found. If I don't do this the card is write protected. I've made sure only to disconnect from PC after "safely removing hardware" so it appears that usage in the phone is generating the confusion. This doesn't seem to be an issue but I thought it might be worth mentioning :D
[Verizon Samsung Galaxy S III] boricua1213:
do you enter it correctly?

I get this when running the script:

BREAK! /dev/block/mmcblk1p1 is not a block-special file/device, do you enter it correctly?

How do I find what block file I need to change to script to?

Thanks for your work
[Verizon Samsung Galaxy S III] HMkX2:
Safest (not easiest) way is to insert your FAT32 card, type "mount|grep vfat". The one you are looking for says "/dev/block/vold___:__" . (Shortcut: "mount|grep vold");

Then type "blkid". The one that's listed twice (UUID or Label) as "vold" is your block device's other name. (/mnt/block/mmc_somethingorother) Both names lead to the same spot.

(or)

Type "blkid" with your card in. Make a list. Remove your card. Type "blkid" again. The one that dissapears is your block device.
[Verizon Samsung Galaxy S III] lordazoroth:
Ok got the file, I created 2 files, 1 before and 1 after the force unplug, just in case.

Remember to rename the files without the .rar extension before use :D
[Verizon Samsung Galaxy S III] spearoid:
Re: [MOD] 1-Click Flashable exFAT + NTFS + EXT4 support for CM10.1 / AOSP (external S

I am about to embark on this journey and make another attempt at ditching TouchWiz. Does this script make it as if everything is normal as far as apps accessing the SD card go? I assume so, but I'm specifically wondering if I'll still be able to use Directory Bind and if I'll be able to create symbolic links to redirect Google Music to the external SD.

Getting ready to flash and try anyway but figured I'd ask to see if someone knows the answer all ready.
[Verizon Samsung Galaxy S III] spearoid:
I'll be the first to admit the problem is almost certainly user error on my part but I have been wholly unsuccessful with this mod. I have tried it on Carbon Rom and Paranoid Rom. I guess they both have FUSE support, I couldn't find any confirmation of that on the Rom threads....particularly Carbon.

I flashed the zip in the OP in CWM after installing both Roms clean. I tried installing the zip as soon as I installed the Rom and I tried installing it after doing a full boot up first. Ran the chkdks /f command probably 12 times after each successive failed attempt to get my 64 exFAT card recognized. Said Damaged SD no matter what I tried. I saw the post on Page 1 about deleting the fixmyfat file....tried that too and no go. That tip may no longer be relevant since you've updated the script.

Is there something I am missing? There are lots of posts in this thread about mount commands and adb, but it seems from the OP none of those things are supposed to be necessary.
[Verizon Samsung Galaxy S III] HMkX2:
In short, it should. However, exFAT/FAT32 don't support permissions/softlinks like ext4 does. So if you use ext4, just remember to set permissions appropriately! When in doubt, set permissions to 755 root:sdcard_rw or root:media_rw on the external sd.

I have tried it on Carbon Rom and Paranoid Rom. I guess they both have FUSE support, I couldn't find any confirmation of that on the Rom threads....particularly Carbon​

Type "mount | grep fuse" in console. If you see "fuse" listed anywhere in the text, you have it. Google added it to JellyBean.

I flashed the zip in the OP in CWM after installing both Roms clean. I tried installing the zip as soon as I installed the Rom and I tried installing it after doing a full boot up first. Ran the chkdks /f command probably 12 times after each successive failed attempt to get my 64 exFAT card recognized. Said Damaged SD no matter what I tried. I saw the post on Page 1 about deleting the fixmyfat file....tried that too and no go. That tip may no longer be relevant since you've updated the script.

Is there something I am missing? There are lots of posts in this thread about mount commands and adb, but it seems from the OP none of those things are supposed to be necessary.​

Do me a favor... open a terminal, type "su", then type "fuse-mountsd.sh > /sdcard/debug.txt 2>&1" (no spaces in 2>&1). It will make a "debug.txt" file in the root of your internal storage. Paste the output here. I am 90% certain you have the wrong block device set. 9% certain it is the 4.2.2 ADB thing.

You do not need to delete "fixmyfat.sh" -- those instructions are very old. Was the phone *physically off* when you plugged the SDcard in? Ignore the mount commands/ADB - you should not have to deal with them if you only plug in/unplug the card when the phone is off.

I am nigh certain it has to do with 4.2.2 messing with ADB. Like I said, for now, put in a *working* sd card *before* the phone is turned on and you won't run into that issue.
[Verizon Samsung Galaxy S III] HMkX2:
Thanks, that helps a lot. Yeah, it was as I suspected.. I bolded/red the relevant parts. Can you tell me what ROM you are running on your Note II GT-N7100?

Your "mount" command is outputting a different format than it normally should. On my phone (GS3 CM10.1 4/18/2013) the "mount" command the output should be this:

/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

(Note: this is the same as "cat /proc/mounts" which was displayed in your first post/my program's debug. Technically, they SHOULD output the same thing.)

I will rewrite the script to use "cat /proc/mounts" instead wherever possible for 6.4 and re-post it, should fix Problem #1. I will also take this chance to remove "conv=notrunc", as it seems to be unnecessary safety.

As for permissions, I have no idea why you do not have a "media_rw" user. (It should be built into Android!) This is a shot in the dark, but try using "sdcard_rw:sdcard_rw" instead and see if that works. (Type "ls -al /storage/emulated/legacy" and look at who owns those files, it should provide a hint.)

If that too fails, you will have to set permissions to (insecure) 777. (give EVERYONE full access)
[Verizon Samsung Galaxy S III] KrzysztofGW:
On my N7100 NTFS (AOSP 10.1 - HyperDroid AOXP) worked well. But I started wondering if it generates little battery drain, but rather not...

Good shot - sdcard_rw is my use name (or group name - I really don't understand Android users). So I fixed it, but partially. Now I can at least open files that were on sdcard before activating comand. Also copying files from Win7 works, I can create folders but cannot rename them. As the result I get two folders: renamed which is broken and "New folder" (both are visible only on the phone).

So than I copied my backed up folders (DCIM content and deezer) from PC and downloaded random image from Internet - result below:

u0_a67@android:/ $ ls -al /storage/sdcard1/
-rwxrwxr-x sdcard_rw sdcard_rw 5324864 2013-04-20 00:23 52 Dbiec - To My.mp3
-rw------- u0_a15 u0_a15 133395 2013-04-21 11:40 748deb06c2154b669528af9df7eed738.jpg
drwxrwxr-x sdcard_rw sdcard_rw 2013-04-21 11:40 DCIM
-rwxrwxr-x sdcard_rw sdcard_rw 368042 2013-04-20 00:23 PPP_harmonogram_2012-2013.pdf
drwxrwxr-x u0_a11 media_rw 2013-04-21 11:38 deezer
drwxrwxr-x sdcard_rw sdcard_rw 2013-04-14 13:54 lost+found

Taking photos works partially. The file is created (normal file size), but I cannot open it. The same the downloaded picture. And suddenly media_rw appeared :)
[Verizon Samsung Galaxy S III] HMkX2:
I bolded/red the important part. Your card has weird partitioning -- likely Logical partitions (p5). It sees size 0 partition 1 (the primary partition) and gets confused, and defaults into my multi-mount code. The result is the card is mounted under /storage/mmcblk1p5.

Two potential fixes: upgrade to my script version 6.5 (where I have changed the logic somewhat for people like you) or create a ".mounthere" file in your SD-card with the text "/storage/sdcard1".

echo "/storage/sdcard1" > /storage/mmcblk1p5/.mounthere

That's.... interesting. Yeah... let's go with that.

One last suggestion, try "root:media_rw" or if that fails "sdcard_rw:media_rw". If even that fails, use the "777" permissions.

There is another potential solution that makes use of the "sdcard" binary command (it's what the phone uses to mount EXT4 /data/media/0 as fake-FAT /storage/emulated/legacy FUSE wrapper), but I need to reformat my card to get it working and give instructions. Type "sdcard" in a terminal as root and you will see the invocation -- I haven't had luck using it since I don't have the instructions.
[Verizon Samsung Galaxy S III] HMkX2:
lol so I just had a major breakthrough. I got the "sdcard" FUSE wrapper working... with any filesystem. This should fix the permission issues present with EXT4.

Will post back later when I have solid instructions.

For now, the important bits for working EXT4 MTP access are: 775 on "/storage/sdcard1" with owner/group <doesn't matter>:media_rw . (I suggest root:media_rw for greatest flexibility, and have edited OP accordingly.) This allows folders to be created, renamed, and deleted at will.

Edit: It seems the newest version of Mastamoon's CM10.1 supports EXT4 natively. To anyone having issues, delete my files and it should work now on its own.

http://review.cyanogenmod.org/#/c/31215/

This was merged some time between the builds I use -- oh well. I will edit 6.5 to remove EXT4/3/2 support, as it is no longer needed.

Edit 2: I take that back. CM10.1's implementation is not quite there yet -- and runs into the same problem I discovered sdcard daemon not terminating cleanly. Using CM10.1 builtin EXT4 you eject the card and reinsert repeatedly, your phone will have a race condition and lock up. I'll leave mine as is for now.
[Verizon Samsung Galaxy S III] iDielord:
Thanks mate, i didn't really understood how to create this .mounthere file,but i just opened my SD in Partition Wizard and there was Logical partition with some unallocated space before it, so i just reformated card to Primary partiotion and all worked perfectly thanks.
[Verizon Samsung Galaxy S III] Lazar81:
This is a great mod.. searching for this for a long time.. thx for this work
[Verizon Samsung Galaxy S III] jasonxlee01:
Sweet, this works perfectly on Liquidsmooth. Even though my card is formatted as exFAT, I'm not having any issues where my phone doesn't enter deep sleep.
[Verizon Samsung Galaxy S III] okizen:
Where are the options to copy or move files from e.g. the sd card to the internal memory? I'm using the SentinelRom 4.40 on a S3 GT-i9300.
[Verizon Samsung Galaxy S III] ChronoReverse:
So far working on CM10.1 for the Snapdragon GS4 (jfltecan). Hopefully no battery drain as I keep using it.
[Verizon Samsung Galaxy S III] lordazoroth:
Hey this is absolutely wonderful. I've been using this for several weeks now and haven't had any issues (v6.2 w/ exFAT). I had a really quick question, I know it's somewhat unrelated but can the source files be used to give NTFS support to stock ROMs (non-aosp) and if so, how? (I've been looking everywhere and I'm kind of a noob, haven't found an answer, it's ok if i don't get a response, I know it's unrelated :D). Ty so much!
[Verizon Samsung Galaxy S III] alexnakano:
ExFat on Sentinel 4.50-CM 10.1

Sorry about my doubt, but I have flashed this rom on my S3 International - i9300 (http://xdaforums.com/showthread.php?t=2249984).

I don't understand what I have to do: is it only flash this file (CM10.1-AOSP_fuse-mountsd_6.4_HMkX2.zip) after flash the rom??

Or I have to do any other procedure??

I have a external Sd card with 64GB formated in ExFat.

Thanks and sorry about my english
[Verizon Samsung Galaxy S III] c01e:
Installed on CM10.1 running on my SGSII (*Sprint, So E4GT if you wanna go by "their" name.) Working great!, Instantly recognized my new 64GB SanDisk SDXC without issues in exFAT mode. (Note: On sale $62 at Best Buy!)
[Verizon Samsung Galaxy S III] siraltus:
Works perfectly on both my SPH-L900 (Galaxy Note 2 on Sprint) and SGH-T889 (Galaxy Note 2 on T-Mobile) both running latest CyanogenMod 10.1 nightlies. Both have a 64GB MicroSD card with a single exFAT partition.
[Verizon Samsung Galaxy S III] ZuneNinja!:
Isn't exFAT not supported on CM 10.1 ? Is it just working regardless?
[Verizon Samsung Galaxy S III] siraltus:
There is no support for exFAT in CyanogenMod. The point of this mod is to add it.
[Verizon Samsung Galaxy S III] ZuneNinja!:
Wow, I feel dumb. I'm going to give this a try today on my Verizon Note 2. Thanks for the quick reply.
[Verizon Samsung Galaxy S III] siraltus:
No worries. Do remember that you will have to reflash this mod every time you upgrade CM to a new nightly, since CM erases the entire system partition every time it updates itself (including any mods).
[Verizon Samsung Galaxy S III] ZuneNinja!:
So I wiped and partitioned my sd card to NTFS. The Script seems to have worked. I've got a mounted 32 gb sd card and when I type blkid in terminal I see that it has mounted the NTFS partition. The problem is, i'm trying to use the adb-smash.sh script and using script manager. The script appears to work, I don't really see any errors in the text, but my card doesn't actually map to /storage/sdcard0 . All I see is /storage/sdcard1 which is my internal memory.

I'm running CM10.1 on my Verizon Galaxy Note 2 SCH-i605 . What am I doing wrong? How can I get you a debug.txt from that script?

Thanks in advance.
[Verizon Samsung Galaxy S III] Captain_Throwback:
Do you have a .mounthere file on the root of the card telling the script to mount the card at /storage/sdcard0?
[Verizon Samsung Galaxy S III] sg10:
your script work wonderful. exfat sdcard mounted perfectly.

My only problem is transfer rate with MTP = very2 slow. 1-2MB/s

What's strange is transfer using wifi = 3-4MB/s

Transfer using card reader = 9-10MB/s

some problem with MTP driver ?
[Verizon Samsung Galaxy S III] ZuneNinja!:
Ok I think i've got it working after adding the .mounthere file . I guess I was reading it wrong and thought that with using adb-smash that I didn't need to do that. GTA 3 isn't working with using the data stored on the ntfs card, but I've got to mess around with it more. Thanks for the help and the mod!
[Verizon Samsung Galaxy S III] smmiller506:
You, sir, are awesome. I will buy you a beer for this.

Works on a Sprint Note 2, CM10.1.
[Verizon Samsung Galaxy S III] blueride:
Will this work on pac man rom for VZ S4? Thx!
[Verizon Samsung Galaxy S III] Captain_Throwback:
Only one way to find out . . .
[Verizon Samsung Galaxy S III] gerzii:
so i must run a script in cm to use exfat and ntfs? is this righT?
[Verizon Samsung Galaxy S III] edlee:
exFat works great in my samsung E4GT (Sprint GS2), and my device went to sleep after media scanner did its thing.

Awesome tweak, this really made my phone last a little longer.
[Verizon Samsung Galaxy S III] LRiley:
Thanks, works on Verizon gn2(PAC)
[Verizon Samsung Galaxy S III] pogi1100:
Working great on the international version of the S3 (GT-I9300). Thanks!
[Verizon Samsung Galaxy S III] Captain_Throwback:
[MENTION=2327391]HMkX2[/MENTION]

Looks like CM is finally trying to enable exFAT support:

http://review.cyanogenmod.org/45176

How will that affect the usage of this script (once it's tested and merged)?
[Verizon Samsung Galaxy S III] pogi1100:
So my Poweramp isn't detecting my music files in my external SD card (exFAT). I searched this thread and found that the solution was to bind the external SD to a folder in the internal. I used FolderMount to accomplish this. However, the app still won't detect any music in the binded folder. Anyone still getting Poweramp to work with this mod?

Ah, NTFS and exFAT support just got merged :)
[Verizon Samsung Galaxy S III] siraltus:
This mod has been officially merged into Cyanogen 10.1 as of the July 8th nightly. You no longer need to flash this mod, as exFAT R/W (and NTFS R/W) support is now built-in.

EDIT: CyanogenMod 10.1 now supports reading and writing to single-partition ex-FAT- and NTFS-formatted cards natively. If you want to use multiple partitions on your card, you still need to use the script from this mod. Thanks to Captain_Throwback for clarification.
[Verizon Samsung Galaxy S III] Captain_Throwback:
That's not entirely true. The CM implementation doesn't allow for multiple partitions, which the script can/does account for. Since the necessary binaries are now included in CM, however, only the script is really needed now (and it may need to be slightly adjusted for the CM binary names).
[Verizon Samsung Galaxy S III] siraltus:
Ah, good to know, I sit corrected.

Just wanted to let folks now that if all they want is for their exFAT-formatted microSD card to work in CM10.1, it now does with no extra hacks.
[Verizon Samsung Galaxy S III] rascal0pl:
how to do that ?

When I put .mounthere file with "/storage/sdcard0/extSdCard" inside - it is not mounting. When I select another location (/storage/ExtSD for example) it works (it is mounting, but poweramp still does't shows this location)

Everything is working fine but not poweramp, I don't want to use another music player...

I will be grateful for any help (I'm on rootbox, not CM)
[Verizon Samsung Galaxy S III] jauhari:
when this feature will be implemented? On latest nightly (cm-10.1-20130713-NIGHTLY-n7100.zip ) http://get.cm/get/9dL my SanDisk still not readable.

Any clue?

---------- Post added at 04:42 PM ---------- Previous post was at 03:46 PM ----------

Flash it via CWM and work like charm... \o/
[Verizon Samsung Galaxy S III] Phil3759:
Finally,

Here's my working implementation to build a static binary under bionic and recovery:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/b1bbdc2608b5db5e6c400953da42ad68a42b1e09

Here's a ready binary fully working. Enjoy the really smaller size of bionic

http://d-h.st/eVo

Please give your feedback
[Verizon Samsung Galaxy S III] cybernick01:
Hi, I see this only applies to cyanogenmod users? I'm currently using 4.2.2 on the SG3, I just need to fix my sd boot from android (it says damaged/unmountable) but I can't execute the fixmyexfat.sh script (I've placed it in /data). I've tried several ways, any suggestions?
[Verizon Samsung Galaxy S III] Captain_Throwback:
Plug the card into a Windows 7/8 PC and run chkdsk /f.
[Verizon Samsung Galaxy S III] cybernick01:
Thats the first thing I tried.

neither windows nor linux will recognize the card even using different card readers.

I know the card works because CWM can read the data, all my files seem to be intact.
[Verizon Samsung Galaxy S III] Captain_Throwback:
So NOTHING happens when you plug in the card? I'm not saying that the card is readable in Windows, but as long as it shows up, you should be able to run the chkdsk command, even if the card says it needs to be formatted when you plug it in (don't format it, of course).
[Verizon Samsung Galaxy S III] cybernick01:
Nothing at all happened. I gave up and formatted it from android, gonna try to recover the files now with some software.
[Verizon Samsung Galaxy S III] HMkX2:
Thank you Captain_Throwback for keeping this script on life support. I admit I am a bad programmer, I stopped developing when my use-cases were fixed and it worked for 90% of people. You're the man now, dude.

I'll upgrade to the newest CM and re-do whatever is necessary to get multiple partitions working. Maybe make a replacement for DirectoryBind instead.
[Verizon Samsung Galaxy S III] HMkX2:
Yes, entirely possible. Someone did it for EXT4 and it was merged. exFat they hesitated on for moral reasons, NTFS-3g they had no reason. However, their EXT4 version (was) buggy if you ejected/reinserted the card and mine wasn't. They might have fixed that though.

Yes. Install CM10.x, flash the ZIP in recovery. For most people that is all.

Those errors in red mean your "shell prompt" is outdated and not liking the way my Bash script is written. You might need to use an updated version of BusyBox. Type "busybox --help" (I think) to find what version you have.

MTP sucks. That's a known fact. "SGS3 Easy UMS" app fixes that problem.

I made a ZIP which makes my script run by itself when the phone restarts. Technically you don't need to do anything more than flash it.

Hooray! This complete hack of a mod won't be necessary anymore! :D

Hooray!

The CM implementation of EXT4 also sucks, the "sdcard" binary causes the phone to lock up since it doesn't terminate when you eject the card. Zombie processes.

Disable "Directory Creation Security". There are instructions in the top post.

Unless the directory already exists, my script is set to NEVER create one. It can bind on top of already-existing directories, however. This was a security feature meant to prevent newbies from making zombie folders everywhere.
[Verizon Samsung Galaxy S III] lordazoroth:
Ty so much for your reply. You wouldn't happen to know where I can find this project would you? I've scoured the internet >.<
[Verizon Samsung Galaxy S III] Phil3759:
Look at my github.

I added all needed sources to compile static binaries that perfectly mount ntfs 3g

All you need is to run these binaries through some startup shell scripts

A custom stock ROM is even better as it can start it through init.d scripts
[Verizon Samsung Galaxy S III] synpax:
Hey,

So I've been trying to get this SD card to mount in my T-mo Cyanogen phone but no luck.

If someone here would like to make an easy $25 (or I can donate it to whomever), would you mind PM'ming me your skype of phone number so we can deal with this? I'm in the US.