Wondering if anyone has managed to figure out a way to get this working, or if I'm just missing something. I've tried everything I can find online, including a custom kernel (EX), (both) paragon NTFS mounting utilities, stickmount, a couple different TWRP-flashable .zip's, as well as miscellaneous other root apps that supposedly will mount NTFS, all to no avail.
Running 9.0, stock rooted + EX kernel and Magisk. And unfortunately FAT32 or other formatting isn't an option in my case. Any thoughts or advice or is this just a no go? Thanks!
Android doesn't support NTFS and is unlikely to ever support it. If none of the apps you've tried work then there isn't anything you can do except format the drive you want to use as FAT32. I know that isn't an option, but you don't havr many options here.
Paragon "works", but only in a couple of specialized file managers. There's no generic solution I've seen that simply mounts OTG as a directory. There is a Magisk package that claims to do this with vold, but it's only supported by an older Magisk version and doesn't support Android 9 yet.
ohlin5 said:
Wondering if anyone has managed to figure out a way to get this working, or if I'm just missing something. I've tried everything I can find online, including a custom kernel (EX), (both) paragon NTFS mounting utilities, stickmount, a couple different TWRP-flashable .zip's, as well as miscellaneous other root apps that supposedly will mount NTFS, all to no avail. Running 9.0, stock rooted + EX kernel and Magisk. And unfortunately FAT32 or other formatting isn't an option in my case. Any thoughts or advice or is this just a no go? Thanks!
Click to expand...
Click to collapse
Android only supports FAT32/Ext3/Ext4/exFAT. Why is FAT32 not an option? It will support up to 2TB partitions and although it doesn't natively support encryption, it is possible to encrypt data on a FAT32 formatted partition. What is it you are trying to accomplish?
The OP likely has a device formatted as NTFS and doesn't want to go through the trouble of pulling off the data, formatting, and replacing the data. Unfortunately for him, he's going to have little choice but to fornat to be able to use it.
exFAT USB drive wasn't supported on my P2XL Pie, tested a few days ago. Had to format FAT32 through Android (since the only options were FAT32 and NTFS in Windows File Explorer).
i may be a little late to this thread, but
total commander from c. ghisler and
usb stick plugin (tc) from ferenc hechler
does that. it worked on Android 8 at least, on android 9 i have some troubles atm, i can only copy data to my expandable sd card storage, but maybe it's a bug on my hand, worth a shot.
there is a free version of the usb stick plugin as well and total commander was always free without ads
Related
Has anyone had any experience with using their SDcard with either the ntfs file format, or any other? If so, how well did it work and what did you think of it?
I know there are plenty of threads out there asking whether it's theoretically possible to format the SDcard to any other file systems (usually asking ntfs) and still expect android to read it, but I haven't found actual usage statistics (stability, speed). I'm interested in reformatting my SDcard to either NTFS or 4ext (I use linux, so pretty much any file system is game), however I don't know if this will be better for prevent files from easily corrupting, or if it'll still be the same (theoretically it should).
xxkid123 said:
Has anyone had any experience with using their SDcard with either the ntfs file format, or any other? If so, how well did it work and what did you think of it?
I know there are plenty of threads out there asking whether it's theoretically possible to format the SDcard to any other file systems (usually asking ntfs) and still expect android to read it, but I haven't found actual usage statistics (stability, speed). I'm interested in reformatting my SDcard to either NTFS or 4ext (I use linux, so pretty much any file system is game), however I don't know if this will be better for prevent files from easily corrupting, or if it'll still be the same (theoretically it should).
Click to expand...
Click to collapse
I didn't know that 4ext was a file system, I believe you meant etx4 :trollolol: 4Ext is a recovery for some android (HTC) devices.
I recommend using 4Ext to format your sd card with whatever it recommends. I think it formats to part ext3 and the rest as ext4, but I can't remember.
I think you can use NTFS or any other popular formats with android though
Yes but not on the DHD. Kernel support is required for R/W in those formats. For example, the Samsung Galaxy S3 can use NTFS and exfat formatted SD cards. The DHD can only access fat32 formatted cards and use a multi-partitioned (ext3/ext4) card for app2sd.
Sent from my Desire HD using xda premium
sashank said:
Yes but not on the DHD. Kernel support is required for R/W in those formats. For example, the Samsung Galaxy S3 can use NTFS and exfat formatted SD cards. The DHD can only access fat32 formatted cards and use a multi-partitioned (ext3/ext4) card for app2sd.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
thanks, this was what I was looking for!
Fallon9111 said:
I didn't know that 4ext was a file system, I believe you meant etx4 :trollolol: 4Ext is a recovery for some android (HTC) devices.
I recommend using 4Ext to format your sd card with whatever it recommends. I think it formats to part ext3 and the rest as ext4, but I can't remember.
I think you can use NTFS or any other popular formats with android though
Click to expand...
Click to collapse
jeezus, I meant ext4 I us 4ext rc8 on my i4g, so I'll probably give it a go sometime.
I'm not exactly new to linux, or android, but I'm not familiar with how android treats external storage vs. internal.
I had advised a few people to format their external drives as ext4 since the kernel would probably support it (and the system, data and cache partitions are ext4 so it DOES). However, when I format my external storage (32gb and 1gb USB sticks) to ext*, it doesn't show up, even in the logcat or in ES File Explorer (or a mount command, but with no root or fdisk -l i didn't dig too far).
So I was wondering if anyone happens to know why thats the case. Clearly the kernel supprots ext4, but you can't mount external storage with it?
FYI, so far that I've seen, I can't format external storage with the ouya. It also only supports NTFS read, and FAT32 R/W.
kill-9 said:
I'm not exactly new to linux, or android, but I'm not familiar with how android treats external storage vs. internal.
I had advised a few people to format their external drives as ext4 since the kernel would probably support it (and the system, data and cache partitions are ext4 so it DOES). However, when I format my external storage (32gb and 1gb USB sticks) to ext*, it doesn't show up, even in the logcat or in ES File Explorer (or a mount command, but with no root or fdisk -l i didn't dig too far).
So I was wondering if anyone happens to know why thats the case. Clearly the kernel supprots ext4, but you can't mount external storage with it?
FYI, so far that I've seen, I can't format external storage with the ouya. It also only supports NTFS read, and FAT32 R/W.
Click to expand...
Click to collapse
I've asked this question too, I tried with different harddrives to all the ext formats and nothing picks it up. there are a few apps like ntfs mounter which supports ext but requires rooting.
Android only recognises FAT32 and I think CDFS and UDF. May also recognise FAT16. NTFS and exFAT are both patented so need expensive licenses for a manufacturer to include them in devices (a few do on their modified firmwares).
I have no idea why ext isn't supported though. I presume it is something to do with the relative rarity of ext drives outside of Linux boot devices.
SixSixSevenSeven said:
Android only recognises FAT32 and I think CDFS and UDF. May also recognise FAT16. NTFS and exFAT are both patented so need expensive licenses for a manufacturer to include them in devices (a few do on their modified firmwares).
I have no idea why ext isn't supported though. I presume it is something to do with the relative rarity of ext drives outside of Linux boot devices.
Click to expand...
Click to collapse
isnt the internal memory ext4?
anyone who has there ouya rooted could you please try one of the harddrive mounting apks like paragon or ntfs mounter and see if the ext formats get picked up?
got ext3 working with usb otg helper app. You need root access.
No problem mounting ext4
Just made myself a 15GB ext4 formatted second partition on a 32GB usb drive. Just because Ouya only looks at the first partition, and assumes it's fat32 should not discourage you. Just open a adb shell to your Ouya, become superuser, create a directory /mnt/mydata, and mount it:
In adb shell:
1. su
2. mkdir /mnt/mydata
3. mount -t ext4 /dev/block/vold/8\:2 /mnt/mydata
kill-9 said:
I'm not exactly new to linux, or android, but I'm not familiar with how android treats external storage vs. internal.
I had advised a few people to format their external drives as ext4 since the kernel would probably support it (and the system, data and cache partitions are ext4 so it DOES). However, when I format my external storage (32gb and 1gb USB sticks) to ext*, it doesn't show up, even in the logcat or in ES File Explorer (or a mount command, but with no root or fdisk -l i didn't dig too far).
So I was wondering if anyone happens to know why thats the case. Clearly the kernel supprots ext4, but you can't mount external storage with it?
FYI, so far that I've seen, I can't format external storage with the ouya. It also only supports NTFS read, and FAT32 R/W.
Click to expand...
Click to collapse
Not Actually True
SixSixSevenSeven said:
Android only recognises FAT32 and I think CDFS and UDF. May also recognise FAT16. NTFS and exFAT are both patented so need expensive licenses for a manufacturer to include them in devices (a few do on their modified firmwares).
I have no idea why ext isn't supported though. I presume it is something to do with the relative rarity of ext drives outside of Linux boot devices.
Click to expand...
Click to collapse
There is in fact a standard read-only NTFS driver in LInux, and it's supported on the OUYA. An NTFS-formatted USB hard drive automounts upon hot plugin.
I finally got a reply back from ouya support about ext3/4 not being recognized and they said its been resolved. Looking forward to the next firmware.
I just got a FireTV, it's rooted, on the latest pre-rooted 51.1.4.1_514013920
I've tried to mount a few USB flash drives (16-64GB, NTFS or FAT32 formatted) via a USB hub and directly plugged into the USB port on the AFTV. I can't get it to work. I'm using the latest version of StickMount installed from the Google Play Store and also tried adbFire the USB mount option.
StickMount doesn't do anything and if I try to click Mount or Unmount again it says the service is busy.
adbFire shows a /usb/drive1 via SMB but it's empty, it's not the actual flash drive.
How do I troubleshoot this? I must be missing something simple.
hi you could try Busymount: http://forum.xda-developers.com/fire-tv/development/busymount-v1-0-t2920146
which mounts the drives on boot, much better than stickmount and can be customized to your needs.
Uninstall Stickmount first though as i think they conflict.
DEREKTROTTER said:
hi you could try Busymount: http://forum.xda-developers.com/fire-tv/development/busymount-v1-0-t2920146
which mounts the drives on boot, much better than stickmount and can be customized to your needs.
Uninstall Stickmount first though as i think they conflict.
Click to expand...
Click to collapse
Thanks, I'll give that a try. I should also try to see first if I can see the USB flash drive from CWM, it will at least tell me everything is fine from a hardware perspective.
I installed BusyBox via adbFire, is there some other version of BusyBox required? BusyMount says it comes with BusyBox but I'm not sure whether that means it replaces any existing BusyBox or it installs its own version for its own use.
Also, what is the recommended format for external flash drives for best performance, to be writable and to be able to use from CWM to flash new ROMs, etc.? ext4, FAT32? Does it matter?
sirxdroid said:
Also, what is the recommended format for external flash drives for best performance, to be writable and to be able to use from CWM to flash new ROMs, etc.? ext4, FAT32? Does it matter?
Click to expand...
Click to collapse
im not sure what formats work best but it depends on the type of files. Ive always used NTFS for big drives and FAT32 for flash usb.
and i installed it via adbfire also, think that is all u need.
I was wondering if anyone could point me to a way to be able to use an ext4 formatted sd-card with a stock lollipop ROM?
I'm usually using CM which had this built in, but might have to revert to stock due to an annoying lag with a Bluetooth keyboard on cm.
Marshmallow uses encrypted EXT4 for Adopted Storage. With LP it shouldn't work at all. At least stock Note handles exFAT, which the custom roms don't. More annoyingly, the Note doesn't support USB to Go media with NTFS.
Thanks! That's a shame, so no way to get ext4 support even with one of the custom kernels? I tried searching, but didn't come up with anything conclusive (and the xluco kernel I tried didn't seem to help). I did try an app called ntfs mounter, which claims to Mount a range of formats, but it didn't seem to work either.
And it seems not even exfat would be a reasonable alternative? I'd like to avoid it anyway, as Linux support isn't great (and it feels wrong not to use ext4 if you're using Linux anyway). What I would need if I were to try the stock ROM is some way to have files larger than 4gb for my Linux chroot image...
Initially Titanium Backup's "move to SD" feature looked like a great way to use tools I was already familiar with to make the most of limited internal storage. While searching for answers on how to set up what TB needed, it became clear that pretty much any similar app or solution - e.g. Mounts2SD - would need this partition mounted to function properly.
Problem is I can't seem to get it to work, despite trying EVERYthing that all of xda forums and Google can tell me. And there's a lot of info on this topic.
This is the mount command in Terminal emulator:
Code:
su
busybox mount -t ext4 /dev/block/mmcblk1p2 /sd-ext
(where I've confirmed that /dev/block/mmcblk1p2 is the partition I want to mount, ext4 is replaced by correct filesystem, and /sd-ext exists and is the desired mount point.)
It seems to go fine... I don't get any errors or feedback. But TB doesn't detect the partition even after adding an "app" folder using "mkdir" command.
Here's way more info than necessary about my situation in case it might help...
Device is SM-113, KK 4.4.4. Rooted, stock everything, selectively debloated using Titanium Backup Pro
Recovery is TWRP 3.0.0
Busybox by Stericson from Google Play
This is what I've done, in all possible combinations:
— Have used 3 separate SD cards: 32GB fresh out of the package (largest size officially supported by this tab) and 2 used 64GB (no documentation but it mounted and works fine for regular storage!)
— Used TWRP, AParted (from Play store) and Minitool (on Windows) to create the partitions
— 2nd partition formatted as ext2 & ext4 (read somewhere that ext3 wasn't a good idea...)
— Size of the 2nd partition ranging from less than 10% of SD card size up to 10GB
— Mounting to /sd-ext, /system/sd, and /data/sd (per TB's knowledgebase, linked above )
I've also attempted using a few apps from Google PIay as recommended by various threads on the subject from this forum (don't even remember which but I can look them up if necessary). I've since wiped and restored a nandroid backup so that none of these can potentially get in the way.
This IS working on my (also stock, MM 6.0.1) Galaxy S5 (G900W8) with one of the cards that didnt work on this tab - a 4GB ext4 partition on a 64GB SD card. After TB recognized it I set up init.d support and it happily mounts on every boot.
So it looks like it's something to do with this device, which sadly has extremely limited space that makes me want to cry. Therefore, I hope someone else with the 113 can lend a hand.
If necessary, I'm totally willing to flash stock, re-root, and set everything up again in order to make this work!
Not too sure. I use Aparted and Link2SD on a couple of my older toys...lol. I use ext 3 too. I have a 210, I'll play with it and see if I can figure it out.
Thanks @RealWelder! Don't know if that'll help as it's a different device, but let me know what, if anything, you figure out.
Personally, I'm going to give it another shot using the 'Mounts2SD' app (even though I'd wanted to do this WITHOUT any new apps... oh well, if it works at least I'll have plenty of space!)
I got it to work! *happy dance* Absolutely NO idea exactly what did it, but there was a lot of fiddling with permissions, and rebooting, and painfully typing "mount -t ext4 etc. etc." into terminal, and making adjustments to init.d scripts until finally ... TB recognized it.
Thank you XDA forum!
Sent from my Samsung SM-T113 using XDA Labs