[fuse-mountsd v4.0] exFat+NTFS autorepair and mount script (HMkX2 CORE//XDA)
Automated mounting and repair of alternate SD fs on GS3 CM10.1 [+AOSP Roms!]
BREAK! /dev/block/mmcblk1p1 is not a block-special file/device, did you enter it correctly?
Resetting ADB loopback connection/root security to PRIOR...
/system/xbin/fuse-mountsd.sh: [: -ne: missing second argument
Nobody is dunce, you just haven't learned everything yet. I changed name to fuse-mountsh.sh - my typo in the OP. (When I added EXT4/NTFS support it didn't make sense to call it exfat-mountsd anymore.)Sorry to be such a dunce but the first piece of info I see missing is what you list as the hard coded string of text already. But I do see other text that doesn't appear when running blkid after removing the SD card.
Also, I can't even find the file to edit in your zip file that is mentioned in the OP. I see mount.exfat-fuse but not exfat-mountsd.sh . Of course I'm just unzipping and looking in the xbin folder. That may be wrong.
If you reformatted the card, you no longer need to delete the p1!!! This feels like Benny Hill. (You do not need my script for exFAT on TouchWiz, Samsung paid M$ for it!)
Do these in this exact order and I guarantee you will have a working card:
And the point is you can *eject* the card from System Volume Manager in Android, but to RE-MOUNT it and get rid of the error, you have to run the script! Clicking "Mount" will do nothing -- since the ROM handles that. You need to open a terminal and type "fuse-mountsd.sh <enter>".
- Open Rom Toolbox. Edit the line to say "/dev/block/mmcblk1p1" and click the "Save" icon in the top right.
- Power off the phone. Eject the card.
- Stick the card in Windows. Open a command prompt and type "Chkdsk /f <your drive>"
- Stick the card back in the phone. Turn it on.
... but Linux doesn't support creating exFAT... yet. :laugh: :laugh: Maybe I'll just add /dev/block/mmcblk1 as a default option to expand coverage from the 70% of CM10.1 users to the 99% of regular users.Maybe that just needs to be part of the OP instructions. "Make sure you've formatted the card from your phone or Linux, not Windows"
Just flash the zip. It handles everything and has the NTFS binaries included.Quick question, what happens if I flash the updated zip over my original which gave me exFAT. Would I be able to read NTFS afterwards and how would I go about updating safely?
delete("/system/etc/init.d/50exfat-mountsd"); <- Replaced with 50fuse-mountsd
delete("/system/xbin/exfat-mountsd.sh"); <- Replaced with fuse-mountsd.sh
delete("/system/xbin/dumpexfat"); <- None of these work anyway
delete("/system/xbin/exfatlabel");
delete("/system/xbin/exfatfsck");
delete("/system/xbin/mkexfatfs");
Looking at their script, I see no reason it should not work if you change some of the block devices around. (They used "/dev/block/vold/179:49" and "/dev/block/vold/179:17" for the Note2, which are inappropriate for the GS3.) From looking at it I can actually see a couple of problems with that script on a basic level. (For instance, they do no version checking and it is not coded for JB's per-user "/0/" storage.)Hi All, do you think i would be able to use this mod in conjunction with ExtSd2InternalSd that way i would be able use cm10 and and use my exfat 64gb sdxc as my internal card?
find /storage/sdcard1/ -print0 | xargs -0 chown media_rw:media_rw
chmod -R 775 /storage/sdcard1/
(or)
find /storage/sdcard1/ -print0 | xargs -0 chown root:media_rw
Changelog
[I]7.0 - TBA (Make GUI? Fix ext4 permissions automatically? Get paid?)[/I]
6.4 - No longer uses "mount" output (wasn't acting standard-ly. Using /proc/mounts instead)
- [COLOR="Red"]Got rid of conv=notrunc[/COLOR]. Be careful!
6.3 - Bugfix to scrubMount code
6.2 - No longer Experimental / final unstable
- added rough ext2/3 support
6.1 - mount command bugfix
6.0 - Added a bypass for Directory Security, fixed some bugs.
5.9 - Rewrote NOGO code from scratch -- UUIDs ignored
5.8 - (??)
5.7 - Support for Note2 formatted exFat cards + more (0xf4 bug)
5.6 - bug fixed: no longer detects zram/assumes multimount
5.5 - [COLOR="Red"]Experimental support for weird devices[/COLOR]
5.4 - [b]Major bugfix!![/b] Fix fixmyexfat.sh coding fail
5.3 - Fixed "vffat" support. Undid HARD QUIT on bad Nogo, made it a soft one.
5.2 - Increased logging of tables, HARD QUIT if Nogo not found
5.1 - Quick patch to fix dm-* device blacklist
5.0 - [b]SUPPORTS MULTI-PARTITIONED CARDS! Autoscans for block devs! Complete rewrite![/b]
4.1 - Quick patch to check mmcblk1
4.0 - [B]WORKS 100% ON 4.2.2!![/B] My script is the first to achieve this AFAIK
3.3 - fixed a bug detecting existing mounts (related to "non-persistent mount points" issue)
3.1 - added dynamic exFAT repair code
3.0 - added NTFS/ext4 support
1.0 -> 2.0 <Removed>
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.(..) 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?
Yes. Install CM10.x, flash the ZIP in recovery. For most people that is all.(S3 International - i9300) (..) is it only flash this file (CM10.1-AOSP_fuse-mountsd_6.4_HMkX2.zip) after flash the rom??
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.(MediaTek based devices, both running AOSP ROMs. V987 is running Android 4.2.1 and V970 is running Android 4.1.1.) Both devices have init.d support, but after installing your zip files through recovery mode, the devices weren't able to properly mount the exfat formatted sdcard. While trying to mount it manually, I got the following output:
Code:~~~~~~~~~ Beginning FS Logic ~~~~~~~~~ [COLOR="Red"]./fuse-mountsd.sh: line 940: local: can only be used in a function ./fuse-mountsd.sh: line 941: local: can only be used in a function[/COLOR] Index (0) - [/dev/block/mmcblk1p1\texfat\tmount.exfat-fuse\t-o rw,dirsync,noatime,umask=0\tfixmyexfat.sh] [COLOR="Red"]./fuse-mountsd.sh: line 952: [: too many arguments ./fuse-mountsd.sh: line 986: local: can only be used in a function ./fuse-mountsd.sh: line 987: local: can only be used in a function [/COLOR] (...)
As I'm not yet familiarized with your script, do you have any idea of what's happening?
MTP sucks. That's a known fact. "SGS3 Easy UMS" app fixes that problem.(...)
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 ?
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.so i must run a script in cm to use exfat and ntfs? is this righT?
Hooray! This complete hack of a mod won't be necessary anymore!@HMkX2
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)?
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.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).
Disable "Directory Creation Security". There are instructions in the top post.(..)
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)
My only question is: Even though this is written for CM10.1 on Verizon s3, might this also work on T-mobile s3 with an AOSP (Android 4.2.2) ROM?
(No Eject button: ) Weird.... very weird. Can you open a terminal as root and type "vold" and tell me what it says, or if that fixes it?As you can see on the screemshot, there's no "Eject SD Card" option in Storage Manager. Also, a picture on /storage/sdcard1 doesn't show up in the Gallery. PowerAmp recognizes ordinary fat32 formatted ext card just fine, but not ntfs/exfat.
I disabled autoscanning for media on boot. That was most likely what was causing it. It will now only autoscan for media when the script is run manually (6.0).I seem to have similar issues, but I don't understand how the script could be the issue. (YouTube crash)
... my old device I9000...
Well gave the 5.9 Experimental a run on the device, produced 3 logs - one with 4pcs ext4 partitions, second a log with no sdcard, third a log with the exfat sdcard from my camera.
Results:
R/W on exfat works real nice for posting photos on social services on the net - without the PC.:good:
Same results as 5.8 ""tested a 4 partition sdcard all ext4 with different mountpoints - all four partitions mounts - but the mounts of directorys (3pcs) (/sdcard/somedirectory) does not mount as writeable only readable the last EXT4 partition (/storage/sdcard1)mounts as it should r/w .(the .mounthere works)""
ls -al /sdcard == sdcard -> /storage/emulated/legacy
ls -al /storage/emulated/legacy == /storage/emulated/legacy -> /mnt/shell/emulated/0
mount|grep emulated == /dev/fuse ([I]this is a "fake" vfat filesystem of /data/media)[/I]
[B]find /data/media/0/Download -print0 | xargs -0 chown media_rw:media_rw[/B]
[B]chmod 775 /data/media/0/Download[/B]
or some combination thereof. (root:media_rw / root:sdcard_rw, ??)
I had to comment out the safety check lines (below) before it would create/mount my .mounthere file, but I assume this is still intended to remain in place as a safety and I will have to comment this out on each script update?
dirSECURITY=1