Had this problem with Pie roms as well, but settled on Bootleggers, wasn't an issue with that. Have been playing around with the Q roms now, and am seeing it again with all but Havoc so far. Device is US998, and card is formatted ext4. With most of the roms, it says "card not supported" and gives me the option to format it. In addition to not feeling like shuffling around 64 gb of data, I'm not sure what format it will format it to (this is for media storage, not internal). Definitely don't want exFat, as I've had a bunch of problems in the past with the partition table getting corrupted and needing a windows box to fix (can't be done in linux). Was hoping there was a kernel fix for this. I've tried a couple without success...
Bump... Anyone?
nola mike said:
Bump... Anyone?
Click to expand...
Click to collapse
Don't really have anything to add other than, I bother to shuffle the data if it's a rom I want to use. It seems many of the aosp based roms format it to 'fuse' of some kind. Don't think there's any other option but to use what's built into the rom.
cheers
There isn't enough info provided in the OP, so I have to ask: Is the rom designed to support ext4? Not all roms are... Android doesn't natively support it, from what I'm reading. You have to do something to add support for it (and/or you may still need to manually mount it via root). I also read that CM added this support to their releases...
Some info on how to mount manually, and other related questions: https://android.stackexchange.com/q...-system-for-microsd-cards-in-stock-or-non-lin
Either use ROMs that support Ext4 like Lineage OS and a few others or change your sd card to a different format
Also changing the kernel also affects ext4 compatibility
Related
Is it possible to repartition my SD card to use EXT4 instead of FAT32, with the Fascinate? I'm currently running an EB01 kernel and a custom EB01 build. I'm just not sure how to do this part, as I've never done it before. I've seen it done for other devices, but I don't think it has come up here yet. This isn't really a debate on if I should or should not make it EXT4, just on how to do it.
That's what a voodoo kernel does.
Sent from my SCH-I500 using Tapatalk
JoeDat said:
That's what a voodoo kernel does.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm running the EB01 voodoo kernel, and yes it obviously has support for EXT4 since that is the FS it uses.
My question though is how can I mount my SD card to be recognized when I format it to EXT4 too?
Ah crap. I should have read your post more than once. Mundane detail. Just call me Michael Bolton.
Sent from my SCH-I500 using Tapatalk
If you don't have anything on your SDcard you mind deleting (or could just back it up), you could always try repartitioning it, and then seeing if Android is able to mount it.
If it doesn't automatically work, it shouldn't be too hard to modify the system to work (either by switching it from using 'vfat' to 'auto' or 'ext4')... it's just a matter of finding out where to change it.
There's no reason why it wouldn't, I guess... worst case you use command line mount tool to mount it manually every boot
That's what I thought too, that it would work inherently, but I partitioned/formatted the entire thing to EXT3 and it was not able to be recognized. I think either A) there is no built-in module for EXT3 support, or B) I'm just not doing it right.
Could be that I used a Windows tools to do the job to get EXT3, and I'm having trouble finding one to do EXT4, and I can't find any tools/scripts to convert EXT3 to EXT4 for Android.
If you format the sdcard to anything other than FAT32, Windows will not be able to read it when you try to mount it on your PC. I'm not sure if there are any utilities available that allows Windows to directly mount EXT filesystems or not, but I would be very afraid of data loss with a configuration like that.
What is the reason you want to convert it? Is it the file size limit of FAT32, or something else?
Posted from my EB01 SuperClean Fascinate with Voodoo
ivorycruncher said:
If you format the sdcard to anything other than FAT32, Windows will not be able to read it when you try to mount it on your PC. I'm not sure if there are any utilities available that allows Windows to directly mount EXT filesystems or not, but I would be very afraid of data loss with a configuration like that.
Click to expand...
Click to collapse
There's been an ext2 (possibly 3/4, but all are backwards compatible long as you don't use extents on 4) driver for Windows for a number of years. There's also a number of tools that can allow you to open ext2/3/4 file systems and modify them, without actually having to mount them.
ADB would also still work, so would an app that provides access to the sdcard via webdav/ftp/sftp/etc.
What is the reason you want to convert it? Is it the file size limit of FAT32, or something else?
Click to expand...
Click to collapse
Speed should improve by quite a bit, as well as greatly increased reliability (although the windows. Ext2/3/4 also support far larger files than fat32, of course, so if you like your raw-DVD rips or 1080p ultra-high-quality bollywood movies, there would be an obvious benefit by removing that restriction. I don't believe the ext family of file systems support it (but I could be wrong about ext4), but tail packing would greatly improve efficiency if you have a massive number of small files (reiserfs has it, btrfs might also- not sure).
Personally, it doesn't seem like there's enough of a benefit to really do it, especially if you're not using Linux... other than the desire to do it for the sake of doing it... which, considering where we are, that's pretty much enough of a reason to do anything.
Until I can find a good way to automount the FS every boot I wil probably stay with FAT32. I played around with different methods last night quite a bit and it turned into much more of a hassle than I liked. I really regret not having it however, because of the loss of speed.
Please don't flay me alive, have searched the forum, net, front garden.
Very new to Romming my SG2, but had settled on cyanogen 9, as I loved the themes and the speed, battery etc.
All was great until my 64GB sd card stopped working, which after looking up I believe is a known issue with Exfat and CM. After 2 days of trying every way to format my sd to fat32, and having had no joy it seems that my only option is to switch from cyanogen altogether. With that in mind, is there any way to flash a altered sammy rom that is themeable, have had a look through the roms, but not been able to find a rom that is exfat compatible and also themed to black and white. Any ideas folks? Any help is much appreciated. Maybe it's not possible.
I think ExFAT was cut away in ICS.
Connect the SD card to a Linux machine and rewrite the MBR and then format to FAT32.
Cheers for the quick response, unfortunately not got access to a linux machine, am stuck with a laptop, so can't use a live cd even, and the laptop seems to have issue with running a live image from a pendrive. Any other way to achieve this. tried Format /fs:FAT32 in cmd through windows, but fails format every time, tried the hp app, and it only offers me ntfs and exfat. Really would like to keep cyanogen if possible as it's great.
64GB exFAT isn't supported in any ROM, although FAT32 will work.
Will keep trying to find someway to format to fat32
worked it out, seemed Although I was formatting the sd to fat32, the clustersize was wrong seems it need to use 32kb clustersize, which I achieved using EaseUS. Thank gawd.
Currently using a Samsung 64gb micro card formatted fat32 - questions
(1) Does it need to be formatted exfat to take advantage of the TW ME7 updated ROMs? and if so,
(2) Will I still be able to access non TW ROMs with an exfat formatted card? Lastly
(3) Any advantage having a sd-ext partition? Used this with apps2sd pre S4
Tried searching - honestly couldn't find direct answers
tkacer said:
Currently using a Samsung 64gb micro card formatted fat32 - questions
(1) Does it need to be formatted exfat to take advantage of the TW ME7 updated ROMs? and if so,
(2) Will I still be able to access non TW ROMs with an exfat formatted card? Lastly
(3) Any advantage having a sd-ext partition? Used this with apps2sd pre S4
Tried searching - honestly couldn't find direct answers
Click to expand...
Click to collapse
Are you currently on MDK and plan to run ME7 based custom ROM's? If so then you can do custom ROM's. I would format your 64GB card to exFAT anyways given the fact that it supports larger file sizes like movies, etc. I don't see why you wouldn't be able to access the exFAT card with any ROM since I have stock TW ME7 rooted and my card is a Samsung 64GB exFAT format. I hope that helps some.
Raptor -
Tried some ME7 Rom's but they seemed not to be moving the apps to the sd card correctly - when I tried to move them manually, I got a "unable to move - card full" error msg.
I thought perhaps this was because of the fat32 format.
Also like to go back and forth between TW and AOSP Rom's and I thought I read that AOSP kernels don't support exfat????? Also need to check that the recovery I'm using (OUDHs CWM 1.0.3.5) supports exfat. I recall being unable to get it to recognize my card until it was formatted fat32.
Thanks for the reply!
I wonder if there is something in how Samsung wrote that ability into the ROM and the devs may be having an issue with finding the right hooks.
RaptorMD said:
I wonder if there is something in how Samsung wrote that ability into the ROM and the devs may be having an issue with finding the right hooks.
Click to expand...
Click to collapse
Could be - I guess I could back up my card, reformat exfat, and give it go. Unfortunately, I'd have to switch recoveries - Shabbypenguin's recovery does not support exfat. Probably give TWRP a go.......
tkacer said:
Could be - I guess I could back up my card, reformat exfat, and give it go. Unfortunately, I'd have to switch recoveries - Shabbypenguin's recovery does not support exfat. Probably give TWRP a go.......
Click to expand...
Click to collapse
I am not familliar with Shabbypenuin's recovery tool, but TWRP has been awesome for me on the last several Android phones. I would give that a go.
RaptorMD said:
I am not familliar with Shabbypenuin's recovery tool, but TWRP has been awesome for me on the last several Android phones. I would give that a go.
Click to expand...
Click to collapse
It has more to do with the Kernel than the actual ROM. Most custom kernels are now supporting ExFat. The only one I have tried lately that doesn't is Elites Kernel but I am sure that will change soon.
I have a 128 GB microsd and I do not want FAT32 on it. I have MIUI 8 (Android 5.1.1) with 3.10.49 kernel, TWRP 3 and root. For some reason mount doesn't work at all, it always produces error "Invalid argument". I tried replacing it with one from BusyBox but it didn't help. Some forum guys told me that I should add the card to fstab (which AFAIK is located inside boot.img), and edit the config of vold (which is located I have no idea where). Also this. All I understood from there is that there is some storage_list.xml and I should edit it. Again, searching through forums led me to this path framework-res.apk\res\xml\storage_list.xml.
But still! I have no idea where this framework-res.apk is located and how do I unpack-repack it.
All info that I'm desperately trying to extract from google is outdated or related purely to cyanogen >_< Please give some instructions
You wrote you don't want FAT32. Other filesystem than that isn't supported by MIUI which is why you won't succeed to show your card content by editing anything. You need a 3rd party libs with your filesystem support.
See here, worked for me http://forum.xda-developers.com/showthread.php?p=61142640
or install a custom app with your filesystem support (eg. Paragon NTFS).It works either.
Sent from my phone by Tapatalk
Dude, that's the f$#@ed up part, you see.
> If you use KitKat
And I'm using 5.1.1 which is technically lollipop.
I'm seeking for a support as close to native as it can be, so I'm not involving any "mounting" crapware, especially Paragon's products, I'm fed up with their ext4 4 windows driver which gave me countless BSODs and corrupted files.
You said that MIUI doesn't support anything but FAT32, but that's not 100% true. It by default supports only FAT32 for external storage. But at the same time it mounts internal storage (which is of course in ext4) no problem. So I guess it's not *unable* to use ext4 (or f2fs, which is AFAIK supported by any kernel after 3.10.*) for external storage, it's just not enabled by default, and the question is how do I properly use that ability of android to mount ext4 (and/or f2fs)
UPD: I have to apologize for posting "also this" in the initial post w/o actually giving the link, here it is.
This is what seems actually related, but I'm too noob to understand what am I supposed to do to mount the damn card
First, the ROM and/or (especially) kernel should have F2FS support, then ramdisk should be modified with fstab edited so it could mount F2FS partitions at boot.
Other than that, it's impossible.
Sent from my ASUS_Z00A using XDA Labs
Hi there. So my problem is quite...extraordinary.
All I want is to use my 128 GB Micro SD card without errors. However, no matter what file system or configuration I used on it, it just won't work. First it won't allow me to write on it. Then it does but won't allow me to delete from it. Then I need to rescan the contents on it for apps to be able to see media. The card is in perfect condition and without flaws I assure you.
The file systems I tried so far are ext3, ext4, FAT32, NTFS, F2FS and VFAT. Tried multiple custom ROMs including Lineage, Pixel Experience and currently dotOS. It seems that file system support depends on the OS' kernel. I've given up on ext4 and F2FS thanks to the problems I mentioned before. So now I want to format my card as EXFAT. It has much better performance and compatibility than FAT32, NTFS or VFAT. Not to mention these three have significant performance change/spikes while writing and deleting. Only problem that not all kernels support EXFAT and so far neither custom ROM that I used had support built in its kernel. My latest developments is that I found a kernel out of 10 that does support EXFAT. It runs by the name Xenial. I just don't really like custom kernels so I want to avoid using them in the future if that's possible.
Any advice? Please.