i couldnt paste a large file to the internel memory like a .mkv video
is there is a way to convert it to ntfs or another way ????
Android 2.3.7 does not support NTFS file format, which means you are "forced" to use FAT32, which means up to 4GB per single file. Split mkv file to 2 (or more) files if need be.
Cholek3 said:
Android 2.3.7 does not support NTFS file format, which means you are "forced" to use FAT32, which means up to 4GB per single file. Split mkv file to 2 (or more) files if need be.
Click to expand...
Click to collapse
Partially right.
The kernel itself does support NTFS - stock. That's how you can mount NTFS drives in USB-OTG mode. However, the OS itself isn't set to be able to format the partition as NTFS (with extra options and extended testing, i did actually, see DoomLord's MSD thread). Unless there is a third-party app or tweak that modifies how android boots and mounts internal SDCard, and by using non-MTP mode, chances are you are stuck at the moment.
kazuni said:
Partially right.
The kernel itself does support NTFS - stock. That's how you can mount NTFS drives in USB-OTG mode. [...]
Click to expand...
Click to collapse
You cannot mount NTFS drives with the stock kernel.
Sent from the Delta Quadrant using a transwarp conduit.
Related
I have few question is there any way to open NTFS using OTG -> mod??
i got axcient old 40 gb hard drive with 2 partion fat 32 is there any way to see both partitions ?
since i can see only on 1
Stock NTFS is not supported.
I have an app on my Dropad called just "NTFS" or something that allows you to mount NTFS partitions. Not sure if its market or something included in Genesis but there's probably an equivalent in the store. Root might be required.
I bought 64 gb card and it works on samsung stock galaxy s3 rom BUT when i switched to Cyanogen10 mod it started showing damaged card,
I know it is because the stock has driver for that card,
My question is has someone ported or can someone please port the driver from stock and make it workable on custom roms.
Thanks.
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Alright trying hopefully this works and doesnt screw up my card.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
didnt work now the phone doesnt even show damaged card, its acting like card is not even inserted.
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
d4fseeker said:
exFAT is not and probably will never be supported by CM9 or 10.
Your card needs to be FAT32-formatted to work.
Click to expand...
Click to collapse
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Disappointed, as I was tempted to try CM, but no 64GB support renders my card next to useless.
Click to expand...
Click to collapse
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Why is this?! Does AOSP not come with exFAT support, it's something Samsung builds into the kernel afterwards?
Click to expand...
Click to collapse
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
i used easeus partition: i deleted partition first and made new one with fat32 file system,
which didnt work, after that i deleted the partition again and formatted using stock galaxy s3 rom and it works again but limited to stock rom only like before.
atleast the card isnt dead.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
ill try this software as well.
d4fseeker said:
How exactly have you formatted the card? Windows onboard utilities won't let you format a 64GB card as FAT32, so my guess is you formatted it as NTFS.
Unfortunately CM cannot read NTFS either, you'll need another kernel for that. (And to date none has been released)
Try the HP Usb Format utility to create a FAT32 partition.
Click to expand...
Click to collapse
I didnt get a chance to try Hp software i cant across this other software and it work.
Thank you though
d4fseeker said:
FAT32 doesn't mean the card is restricted to 32GB, it means a file can be 2^32 bytes long which is 4GB.
FAT64 (ExFat) has a limit of 2^64 bytes per file which equals 16 Exabyte (1Exabyte = 1024 Terabyte)
It's possible for FAT32 partitions to be as large as 8 Terabyte, which is roughly 1000 times the size of harddisks when FAT32 was released.
Windows, for some stupid compatibility reason with a 12 year old operating system (Windows 2000) does not allow to format FAT32 partitions to a size larger than 32GB, hence the usual confusion.
As described above, here is the tool you need: http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml
Click to expand...
Click to collapse
Thanks, though I realised this - the whole reason I need a 64GB card is to copy movies onto there, because I travel a lot... many of them are over 4GB, which is the issue I have with using FAT32.
d4fseeker said:
ExFat is patent-encumbered, meaning every distributed binary copy of Cyanogenmod would theoretically cost the developers the license fee.
(At least for US-based downloads, most other countries see software patents as what they are - ridiculous and unenforceable)
Furthermore -and a very big issue- is the instability of the exFat code for GNU/Linux (and by extension, Android) which causes data loss, corruption and other negative side effects.
It's highly recommended not to use exFAT with Samsung-firmwares either.
Click to expand...
Click to collapse
Maybe I should look at ext3 instead, though then I'd have problems putting it straight into my Windows machine. Though, exFAT has been 100% stable for me so far.
many of them are over 4GB
Click to expand...
Click to collapse
Ok that is a problem for FAT32. You didn't mention it so I assumed you mistook the 32 in FAT32 for 32GB as many people do.
Maybe I should look at ext3 instead
Click to expand...
Click to collapse
Since you should never need to remove or directly access the card (MTP mode or File transfer through 'Samba Fileshare' App) that should be a solution. For your own computers, you could use the following driver:
http://www.fs-driver.org/
It allows read-write access to EXT2. EXT2 being EXT3 without journaling support (and thus fully backwards compatile) that could do the trick.
Pententially you'll need to re-enable the journal again through tune2fs on the Smartphone after having used an EXT2-driver. Not sure though since the journal is only relevant until a clean dismount is made.
You should however also be able to load the NTFS-module in the kernel or recompile the CM10 kernel with the required options.
If you need to plug the SDcard into your computer a lot, that may be the only solution until Gokhanmoral is back.
ArchLinuxARM for the leo (HTC HD2) - Native Boot
This is only tested with MAGLDR 1.13 on the T-Mobile US HD2, though there's no reason it shouldn't work on a global one, as NAND isn't touched.
Working:
Wi-Fi (with NetworkManager)
Not Working:
Bluetooth
2D & 3D Acceleration (though kgsl and freedreno drivers are in use, the userland isn't patched/installed/tested yet)
Audio
Installation (to the third partition of the SD card)
This procedure is intended only for advanced users. By providing a 6GB F2FS image, the system will boot reasonably quickly and not run out of space, however, it can't be stored as a file on the internal memory - it has to be a partition of its own because of the FAT32 filesize limit of 4GB.
You will need at least 3 MBR primary partitions on the SD card. The third one must be 6GB or larger. Since F2FS volumes can't yet be resized, any space above 6GB on that partition is useless. When this scheme is created, gunzip the provided root.img.gz and write it to the 3rd partition. Then, make the first FAT32 (if it isn't already), make a directory in root of the FAT32, and put the the linux kernel zImage.
Booting
Select the directory you created as the Android SD directory in MAGLDR and boot the system. There will be no console, and you will get a jumbled screen during boot. Eventually, lightdm will start up and you will be on your way.
Logging in
The username is "arch" and the password is "arch". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
You can try to get reroute audio by modprobing "snd-mix-htc-leo" and setting the mixer settings. The system wasn't set to do this at each boot due to serious issues with the concept of copying a 2.6.32 alsa driver into 3.0 and just compiling - it barely works and has a huge propensity to hang during load.
Read Me
I realize this will be difficult to install for most users. I did not provide commands because I don't want anyone wiping and formatting the wrong disk. Eventually, I'll implement a way to make this installable via image. The initramfs issues with the kernel I'm using will first have to be investigated, and then the ext4 issues will. Since Arch Linux uses systemd, I can barely get it to boot with kernel = 3.0, let alone 2.6.32. All my other ports use 3.4, which already requires patches to work after the introduction of udevd version 217.
Downloads
root filesystem image compressed with gzip: https://drive.google.com/file/d/0B4WUjKii92l2ZTNraFpVb2tHbVE/view?usp=sharing
3.0.101 kernel (thank you to maniacx at github for initially sharing the source): https://drive.google.com/file/d/0B4WUjKii92l2aGdGLUYxMm9KSWM/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_leo
Also available for:
Nexus 7 2013 (flo): http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
This phone just won't die.
This is what? The 20th OS to run on the HD2?
Hi There Dear friend ...
Hi there Dear @castrwilliam were looking for an OS for my HD2 to use it through Mouse and KB ( USB Host ) is there anyway I can get any os on My HD2 using them ? ( because mine's TS is broken and doesn't work ) ... Thanks in advance
With Best Wishes
Hitman1376
OTG *should* work on this with external power. Bluetooth most likely does not. Do you have an SD card with a 6GiB third partition?
Sure ...
castrwilliam said:
OTG *should* work on this with external power. Bluetooth most likely does not. Do you have an SD card with a 6GiB third partition?
Click to expand...
Click to collapse
I have an 8 GB SDcard ... with external power ? How ? ... Thank in advance
With Best Wishes
Hitman1376
@castrwilliam
Great job!i will download, resize mmc, install, try...
whatever issues you are facing, post them, maybe i can help after squeezing some free time
Main things are issues on the kernel.
When you try to boot with an initramfs that is compressed, you get either "garbage in compressed da" rand the kernel hangs right then - presumably before it even finishes that printk - or "unknown compression algorithm: " and then vorrupted garbage is output. This prevents me from making image boot doable.
I had this problem a long time ago with GCC 4.9 on a 3.4 flo kernel, but I've tried major versions of 4.6 through 4.9 and none get any further. Also, there's a commit upwards of mine that changed the kernel config from using ARM_UNWIND to FRAME_POINTER for debugging. I tried with each.
Also, when you boot with an ext4 rootfs on mmc, any attempt to write to root gets you an Invalid Argument, when the FS is mounted rw... very strange, but somehow I have a feeling it has to do with systemd trying to do something unsupported/untested on 3.0.x midway through boot, and f2fs lets it work either because it doesn't support it anyway, or because f2fs was backported - possibly with features that aren't in the ext4 driver already.
castrwilliam said:
Main things are issues on the kernel.
When you try to boot with an initramfs that is compressed, you get either "garbage in compressed da" rand the kernel hangs right then - presumably before it even finishes that printk - or "unknown compression algorithm: " and then vorrupted garbage is output. This prevents me from making image boot doable.
Click to expand...
Click to collapse
regarding initramfs, we have problems with magldr and 3.0.x kernels, that needs a workaround.
there's a patch for kernel (which you probably have already) for magldr boot, where you need to add 6mb of 00's to initrd.gz (not sure if for initramfs too) in order to boot on magldr
more explained: https://github.com/Gilbert32/androi...mmit/77351b60841f1b53c203b4621ea37ba521fa70a9
wondering why the 3rd partition is not itself formatted to f2fs? It can be done from an f2fs sd recovery.
I can't get this to boot from magldr, I have ~3gb fat32 p1, ~4gb ext4 p2 and 6.4gb ext4 p3
It reboots within about 6 seconds after showing white stripes on screen (just as with boot attempts using 3.0 kernels without the 6mb of zeros in initrd.gz)
I get the attached dmesg
Edit; tried making a file with 6mb of zeros called initrd.gz and putting it in the boot folder on sdcard, but the same thing happens.
feherneoh said:
For me it works with both MAGLDR and cLK
But for cLK I have to do a liveboot from PC using fastboot
EDIT:
Why are you using EXT4 on mmcblk0p3? Seems like that is the problem, as as far as I know f2fs can only be mounted with fs type defined, so probably it will only accept an f2fs partition as root
Click to expand...
Click to collapse
I just assumed it would be ext4 with an f2fs image, no wonder no replies to my first post
will try it with f2fs partition when I have time, thanks
feherneoh said:
just dd the image onto that partition, or format partition, and copy image's contents over
Click to expand...
Click to collapse
Actually I have formatted p3 to f2fs, and am adb pushing it from pc using f2fs sd recovery. It does take time though, been over an hour
Edit; oops it just reported "no space left on device", going to have to resize the partition I think. perhaps f2fs reserves more space than ext4, so needs to be bigger than the 6.4gb which worked when installing to ext4.
feherneoh said:
Don't push the whole image, just the files on it. It should be less than 6 GB, I'm using it from a 4GB card with a 3GB f2fs partition
Click to expand...
Click to collapse
Can't seem to mount the image in windows unrecognised fs
can only think to put the img onto sdcard fat32, loop mount it from f2fs recovery terminal and copy it to p3. Or get Linux on pc.
I just installed this. This is great. Thanks.
Is the display going to be always on?
Deleted... wrong thread
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.