Writing file to Extdcard by using Paragon NTFS,HFS,HFS+ - General Questions and Answers

Hello, I have lenovo a6000 which have android 4.4.4 Kitkat which have 16 GB Extdcard in it. The device is rooted with the official Supersu.zip v2.37 provided by xda Community. Now as you all know that, FAT 32 FS does not allow you to save files bigger than 4GB. So I formatted my memory card to NTFS. Which my mobile doesnt support.
But as many of you guys know that, there is one app named Paragon NTFS, HFS,HFS+ which allows you to mount your NTFS formatted memory card into your android device which does not has the ability to read the NTFS formatted memory card.
Now I successfully came to the stage where I can access all my data (Photos, videos) after mounting my NTFS formatted Exdcard with the help of that app. Let me mention where I have mounted this Exdcard, its here= /storage/sdcard0/Exdcard (Exdcard is the folder I made). Is this right path to mount the Exdcard? Let me tell you that there was also option of sdcard1 inside the /storage folder. But whenever I select that sdcard1 path it says unable to write to sdcard1 when I try to download file via torrent.
I am not able to download any file no matter what is its size. After 2-3 secs it says Download Failed. So where I am mistaking? In mounting path of that Exdcard? Should I have to select sdcard1 instead of sdcard0 path?
The final question is how can I now download 4gb+ file using this app. What is actually is the right mount point in order to save files larger that 4GB+ in it.
And honestly I searched over the internet about this, on google, youtube etc. But didnt find any answer. So I need your help...
Thank You.

Related

Sd card

I have a sd card. i partitioned it using paragon partition manager mounting sd card thru phone. THen moved apps2sd and then decide to delete partition. So i being unable to delete the partition used windows own partition management to delete all the partitions. Then i decided to again partitions the card. Now i can't. Paragon partition manager can't do it. Used the sd split(ques- do we need an empty card for that). My phone storage went to 0 mb. Can anybody help me to again partition it. I really need it with haykuro's 5.02 H as it has only 43 mb free space. Please!!! Help.
Thanks for reading and now please do something
charnsingh_online said:
I have a sd card. i partitioned it using paragon partition manager mounting sd card thru phone. THen moved apps2sd and then decide to delete partition. So i being unable to delete the partition used windows own partition management to delete all the partitions. Then i decided to again partitions the card. Now i can't. Paragon partition manager can't do it. Used the sd split(ques- do we need an empty card for that). My phone storage went to 0 mb. Can anybody help me to again partition it. I really need it with haykuro's 5.02 H as it has only 43 mb free space. Please!!! Help.
Thanks for reading and now please do something
Click to expand...
Click to collapse
I haven't used paragon before but I would suggest using gparted through an ubuntu(or some other linux distro) live cd. Basically you download the cd image, burn it onto a cd, restart your computer with the cd in and it'll bring up a little menu that gives you the option to start up in ubuntu off the cd. Then go to System->(can't remember, but it's the second option)->Partition Editor. It has a nice gui and you just choose the last device listed which should be your sd card(check the size to make sure!) and you can create new partitions. Making an ext2 partition correctly in windows is a tad... difficult.
EDIT: actually, you can just use this:http://gparted.sourceforge.net/livecd.php
Help
Can u please help me use it. I have portable ubuntu and now this. Can u provide step by step instructions or atleast give a hint to use it

[Tweak] Vold - NTFS support - v0.2

This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.

Solved! How to swap the internal and external SD cards so apps install externally

If you are like me and bought the 16GB version of our beloved SG3, thinking you could always move apps to the external sd card, then this mod is for you. It swaps the internal and external sd cards so apps install on your external card, because your phone is fooled into thinking the external card is the internal card.
I suggest that if you are going to do this, you should probably do it right after installing a new ROM, and before you install any apps. That way everything will get installed onto the external SD card.
I didn't invent this, Zedomax adapted in from mattiadj. But most people haven't been able to get it fully working, probably due to variations in the init.d function of various ROMS. They'd be able to see the External SD card as the internal SD, but the internal SD would disappear. This method avoids using init.d, and instead uses the app Script Manager to load the script on boot.
After much fooling around, I figured out how to do it so the External SD card and the internal cards are swapped, but you can see both with any file Explorer. I got it working on CleanROM 2.0, but it should work on Beans 10 as well.
Here's how to do it: Warning, if you do not understand the following instructions, or don’t have experience doing these things, you probably don’t want to do this hack. I am not responsible if you a) brick your phone, b) delete your data, or c) get very frustrated. That being said, the most likely failure will be that you only see the one card (the External card).
Back everything up that you care about first!!!!
1. First, I'd recommend making a Nandroid backup of your phone.
2. Next, just to be extra safe, I would backup your internal SD card to your PC. While you are doing that, if you have data on the external SD card, back that up too.
3. Next, I would format your external SD card to fat 32. (You could probably use Ext format too, but I didn’t test that.)If you already have it in that format, and have content on it, this won't affect the content, but back it up just to be safe. It’s probably better to have the Ext SD blank to begin with, you can always copy back its content from your pc.
4. Next copy the contents of the internal SD to the External SD card. This is to avoid confusion about apps and such.
5. Next install script manager free from the play store:
https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd
It will show up on your phone as S manager ads.
6. Download the mod from here: http://downloadandroidrom.com/file/...ternalsd_gs3_fat32orextfat_US_ZEDOMAXv0.2.zip
7. You’ll see a folder called: 11extsd2internalsd_gs3_fat32orextfat_US_ZEDOMAXv0.2.zip
You need to unzip the folder, then go to System/etc/init.d and copy the 11extsd2internalsd file from there to your phone. Put it into the /data directory. Use Root Explorer, and your phone will need to be rooted.
(https://dl.dropbox.com/u/6305/SD Card Hack SG3/11ext file in data directory.png)
Or you can get just the 11extsd2internalsd file here: https://dl.dropbox.com/u/6305/SD Card Hack SG3/11extsd2internalsd
8. Using Root Explorer, navigate to that file in the /data directory. Press and hold the file name until the menu pops up, and click on permissions.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Permissions.png
(Unix geeks set them to 777, and everyone else copy the picture below. Click OK.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Permission settings 777.png
9. Open the script manager app, and select Browse as Root in the config screen. Tell it to remember this setting.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Script manager browse as root and save.png
10. Navigate to the /data directory and choose the 11extsd2internalsd file that is located in /data and click on it. Click on the “Is script” button.
11. Now tap on the buttons that say Su, Boot, and Save. The file name will come up in yellow after the save.
https://dl.dropbox.com/u/6305/SD Card Hack SG3/Script manager setting after save.png
12. Reboot your phone and you should see the swap working and be able to access both internal and external SD cards. The external card will show up as sdcard, and the internal card will show up as extSDCard. Your apps should now install to the external card, since your phone will think it's the internal card. Is that confusing? It was to me too!
Good luck and please share your experiences specifying which ROM you used, so that others can avoid frustration.
Thank you’s always appreciated.
Wonder if this works on asop roms as well.
Please excuse my Galaxy S III, it's a bit Paranoid.
On my X2, this same mod was done via a flashable zip...not sure how it worked, but it was worked perfectly. At some point the roms incorporated the flip flop as part of the Rom. I like the feature because I wouldnt need to move certain app data to my external sd card. Also, I wouldn't have to show tibu where to look for my backups.
Sent from my SCH-I535 using Tapatalk
Clienterror said:
Wonder if this works on asop roms as well.
Please excuse my Galaxy S III, it's a bit Paranoid.
Click to expand...
Click to collapse
What's the consensus on this? Can this mod as posted above be applied to AOSP/CM9/CM10?
Just flashed this on aokp and both sdcard and external_sd are my physical sd card. The internal card is not showing.
Op, can we get an cm10 ver?
Did a little playing around. Below seems to work on cm10 aokp. Can op confirm this is good?
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
maniac2k said:
Just flashed this on aokp and both sdcard and external_sd are my physical sd card. The internal card is not showing.
Op, can we get an cm10 ver?
Click to expand...
Click to collapse
Are you actually flashing it, or using the Script Manager? As far as I know, only the Script Manager approach works.
maniac2k said:
Did a little playing around. Below seems to work on cm10 aokp. Can op confirm this is good?
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Click to expand...
Click to collapse
Not sure, but take a look at the code from 11ext2internalsd file. If it works, and you can see both sd cards, then you've nailed it.
Yeah sorry, im running the script apk. It seems to work. I just dont understand the exacts of the vold/179:97 or if it should be vold/197:96?
When i go into settings/storage, should my physical sdcard stats be showing under internal memory?
Thanks I got mines to work now. Thanks to your suggestions.
Sent from my SCH-R530U using Xparent SkyBlue Tapatalk 2
Update: ive been using the script below for a littlw while and it is working great on cm10. It is best to enable it after a fresh rom install.
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
I need to do this.
MODERATOR.
This is not a Q&A Thread. Needs to be moved to appropriate location.
Apps Did Not Move After Internal / External SD Swap for GS3
Well I thought everything went perfectly because as mentioned, when I go to storage my internal shows my 64g card and internal of 12g now shows as external. However the apps are still on my internal which is now called my external and when I go to app manager it shows remaining space 5.9g. So I am not sure what I did wrong because I have reviewed this several times and started right after I installed a fresh rom . I am hoping someone can help me correct this because basically all it did was change the name of the two drives but apps are still getting installed to original location. Thanks in advance for any help you can give me
Swapping internal>external did not work
i followed all steps as stated above but when I go to File Manager (default), long pressing Internal SD>Details show 1.2 MB and External SD shows 1.8 GB which is not true. I have external SD of 8 GB and internal is 2 GB in my micromax a110 phone.
The steps above did not work to swap the memory but it now shows even incorrect size. I installed Root Browser lite but got no way to chck the size of the SD cards.. Please help
Does this work with the new Verizon Jelly Bean which they are now sending out via OTA? Are there other Verizon S3 Jelly Bean Roms that are known to work with this method? Thanks
Its works on the leak so i dont see why it wouldnt work on the actual vz rom
not working
This is not working with my samsung s duos please help
Any cm 10.1 updates for this?
I am unable to change the file permissions to -rwx-rwx-rwx- whenever I try to change it I get an error that the phone is unable to change permissions.
EDIT:
Successfully changed permissions and followed the instructions as given. Still not working on the international S3, my internal memory is still 16 GB and external 32GB

[Q] Tablet/micro SD card permissions

Hi everyone.
I've got a problem with the permissions of my brand new Micro SD Card. I was copying music files to my card from my pc and tried to delete some on my tablet. It would not let me delete them saying I didnt have permission. I can only read the files I put on it, not modify/delete them or write new ones.
My tablet is running Chromi-X 4.6.1 with _that modded stock kernel. Im not sure how to figure out what my micro SD card it formatted to, but I want to reformat it to NTFS or FAT32 since I think that is the problem. Is there any way to format the micro sd while in the tablet? Also, what should I format to, NTFS or FAT32. Im not sure what to do.
I hope someone help me with this? Thank you
wl123 said:
Hi everyone.
I've got a problem with the permissions of my brand new Micro SD Card. I was copying music files to my card from my pc and tried to delete some on my tablet. It would not let me delete them saying I didnt have permission. I can only read the files I put on it, not modify/delete them or write new ones.
My tablet is running Chromi-X 4.6.1 with _that modded stock kernel. Im not sure how to figure out what my micro SD card it formatted to, but I want to reformat it to NTFS or FAT32 since I think that is the problem. Is there any way to format the micro sd while in the tablet? Also, what should I format to, NTFS or FAT32. Im not sure what to do.
I hope someone help me with this? Thank you
Click to expand...
Click to collapse
Do you have access to a terminal emulator (GPlay Jackpal Android Terminal Emulator)? Do you have GPlay ES file explorer? What size and type of SD do you have (SDHC, Class 6?)
[Edit] First lets make sure you have your MicroSD mounted rw. In ES file explorer, in the left column find Tools, click-expand it, and find Mount RW, click that and open it. What do the radio buttons say for /Removable/MicroSD? If the RO button is dotted, change it to RW. If not, continue below.
Its probably a formatting issue but we need to check directory permissions to rule that out first. In ES file explorer, if you browse over to /Removable and then see /MicroSD as a folder, you may see permissions similar to "drwxr-xr-x" when what you need is "drwxrwxrwx". If this is the case then its a permissions problem. Proceed with the following fix.
Go open the terminal emulator and type the following code:
Code:
su
cd /Removable
chmod MicroSD 777
Which will change mode on the directory permissions to "drwxrwxrwx". The number in the code are OCTAL (4=read, 2=write, 1=execute; Sum=Root User, Group, Others) permissions codes.
If you already see "drwxrwxrwx" and still can't delete or rename then reformat your card from a PC. Quick format twice usually does it. Or you can try to copy everything off the card to PC, then copy it all back. If you want to use it ever for recovery then go FAT32. Otherwise you can go NTFS.
If its a 64GB (or larger) SDHX card, then it needs to be exFAT and you can't use it for recovery.

[Q] Is fat32 the only filesystem supported for microsd?

I tried formatting to ext4 and the phone did not recognize the card. Just wondered if anyone else had sucessfully tried any other filesystems?
Right now 64GB microsd's seem to be the best deal and name brand versions can be found as cheap as $20-25 where 128gb cards will still cost you $70+ and usually involve rebates at the lower end prices.
Exfat and fat32. I have mine formatted to fat32.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Applications that can write to SD card can only write to a SD card format to FAT 32. The system file manager can write to Exfat, but that's it.
Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app
jvs60 said:
Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Syncthing is the same way...you should still be able to use the kitkat workaround though which is to save your files to a folder under the android\data\<appname> folder on the sdcard since each app has access to it's own data area.
I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app
jvs60 said:
I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Try this: http://www.instructables.com/id/How-to-bypass-Android-44-KitKat-external-SD-write-/
damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...
keyra74 said:
damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...
Click to expand...
Click to collapse
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37
famewolf said:
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37
Click to expand...
Click to collapse
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad
keyra74 said:
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad
Click to expand...
Click to collapse
Blame google, not Alcatel. The external sd card issue is due to Lollipop..
That app makes the same change...you can uninstall it after it modifies the file. Simpler for me to just edit the file and push the change.
I'm on exfat on a 64gb. Works fine.
The 200gb I had in my g3 worked just fine.
Just realized the card cost more than this phone...
scatoclysm said:
I'm on exfat on a 64gb. Works fine.
Click to expand...
Click to collapse
+1
My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.
maigre said:
My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.
Click to expand...
Click to collapse
Really not much of a benefit to exfat over fat32...especially if you set cluster size when formatting. I also read about some folks having permission issues writing to the exfat till they reformatted. The samsung 128GB I put in my idol3 worked like a champ.
NooB....Thank Google lollypop for sdcard problems. U can write to sdcard with some apps not all if the code is written for this.
It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people
DarkZell666 said:
It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people
Click to expand...
Click to collapse
Or just keep it formatted as fat32 and skip the above which was my choice.
Just my two cents - why would you want to format SD to ext4? Journaling filesystems don't work very well with flash drives, cells die much quicker.

Categories

Resources