Link2SD can't detect second partition - General Questions and Answers

Link2SD can't detect second partition - General Questions and Answers

Hi guys (I'm from Italy, sorry for my elementar english),
My Samsung J500F (rooted, with stock rom lollipop 5.1.1) have a little problem with link2sd: my phone have a ridicolous memory of 8gb, for this reason I buyed a new SD card of 16gb for create a second partition with minitool partition, the first partition is primary FAT32 and the second is primary ext2. Now I have two partition of 8gb and 8gb. Then when I launch link2sd it seems that it recognize the partition and allow me to choose the type of partition.
But when i tick ext2 (I also tried to do the partition of the SD card in ext3 and ext4) and restart the phone link2sd always show me the dialog of choosing the type of partition. There is not any error message or something like that.
Any suggestion? Thank you all

It sounds like it's detecting the second partition but it is isn't persistent through reboot. This usually indicates S-ON or some other security scheme undoing the mount script.
Check my post from a couple weeks ago and see if it helps. I'm curious.
http://forum.xda-developers.com/showthread.php?p=71988462
---
Sent from my HTCONE using XDA Free mobile app

get a better sdcard. cheap sdcard will not work properly

Related

Partitioning SD card

Hi all,
Is it good to partition my SD card? What is positive and negative ?
Sent from my Desire Z using XDA

SonicSoul95 said:
Hi all,
Is it good to partition my SD card? What is positive and negative ?
Sent from my Desire Z using XDA
Click to expand...
Click to collapse
meaning what? swap and ext4?
swap reduces your sd battery life, but it's said that it's not very noticeable, and it's needed with sense 3.5
ext4 just adds space for apps on sdcard as if they were on phone's rom

I mean swap, sorry.
What do you mean with reduce? And how can i swap my sdcard? Can you post me a thread please ? )
Sent from my Desire Z using XDA

This will tell you everything you need to know to get started.

Okey thanks
Sent from my Desire Z using XDA

I just partitioned my MicroSD card with MiniTool.
First Partition: FAT
Second Partition: Ext2
My laptop recognizes the card through card reader and I can see the two partitions in MiniTool, but my phone (HTC Explorer) does not recognize it. Any suggestions?

Well how are you checking if your phone sees it. Some roms can't use sd2ext. Take a good file explorer like root explorer ans see if there's a folder names sd-ext
Sent from my HTC Vision using xda premium

sulehri said:
I just partitioned my MicroSD card with MiniTool.
First Partition: FAT
Second Partition: Ext2
My laptop recognizes the card through card reader and I can see the two partitions in MiniTool, but my phone (HTC Explorer) does not recognize it. Any suggestions?
Click to expand...
Click to collapse
I simply use the phone's recovery (in my case 4EXT) , which will walk me thru everything, I didn't bother with a swap partition but rather a dataswap option (specific to my rom), and a 2GB sd-ext (Again supported by default on my rom). And used 4EXT to convert all my internal file systems to ext4 filetype instead of ext3 (again my rom supports it, but not all roms do).
Essentially you can partition SD and most everything else via ClockworkMod or 4EXT.
PS: Generally sd-ext should be the FIRST partition. (or second in the case of swap, sd-ext and fat32), since some Roms will not automatically recognize it if not placed in that order. thus another reason to do it via recovery.

Use the recovery on your phone to partition your SD card then plug your SD card into a Linux box and check to see if it's EXT4 using Gparted.

how to get sd-ext before fat32 in 4ext?
kbeezie said:
I simply use the phone's recovery (in my case 4EXT) , which will walk me thru everything, I didn't bother with a swap partition but rather a dataswap option (specific to my rom), and a 2GB sd-ext (Again supported by default on my rom). And used 4EXT to convert all my internal file systems to ext4 filetype instead of ext3 (again my rom supports it, but not all roms do).
Essentially you can partition SD and most everything else via ClockworkMod or 4EXT.
PS: Generally sd-ext should be the FIRST partition. (or second in the case of swap, sd-ext and fat32), since some Roms will not automatically recognize it if not placed in that order. thus another reason to do it via recovery.
Click to expand...
Click to collapse
I'm running mimicry-1.4.0, 4ext touch, same as you. When I ask it to partition my new, 16gig, class 10 card, it asks:
size of first sd-ext, to which I reply 2048
size of second sf-ext, to which I reply skip
size of swap, which I also skip,
and then it does the remainder as fat32.
BUT...the fat partition is at the beginning of the card...not the order the app asked for my input...and I don't see how to change them.
Maybe not being first is okay with mimicry?
thanks for your help,
p-d
ps all my file systems are ext4 on the phone itself.

prairie-dad said:
I'm running mimicry-1.4.0, 4ext touch, same as you. When I ask it to partition my new, 16gig, class 10 card, it asks:
size of first sd-ext, to which I reply 2048
size of second sf-ext, to which I reply skip
size of swap, which I also skip,
and then it does the remainder as fat32.
BUT...the fat partition is at the beginning of the card...not the order the app asked for my input...and I don't see how to change them.
Maybe not being first is okay with mimicry?
thanks for your help,
p-d
ps all my file systems are ext4 on the phone itself.
Click to expand...
Click to collapse
you'll be just fine, this is normal
Sent from my HTC Vision using xda premium

demkantor said:
you'll be just fine, this is normal
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Older s2e may need a specific partition order but both clockwork and 4ext arrange in this order, and the enabler script in my signature needs no apps and works fine with mimicry.
Sent from my T-Mobile G2

[Q] sd partition problem.

hi every one..
i have a problem with my samsung 32g class 10 sd card , i wanted to make a second partition using mini tool, i chose ext2 as a second partition and when i opened link2sd app it asked me to chose the file system of the second partition , again i chose ext2 , it asked me to reboot the device. i rebooted it and when i opened link2sd the same message that asked me to chose the file system of the second partition appeared again and when i chose ext2 this message appeared: "mount script cannot be created. mount invalid argument"
i returned to mini tool and tried both ext3 ext4 with no success. and when i tried fat32 as a second partition it created but when i try to link any app on link2sd it fails to link it.
plz can any one tell me what should I do.
thanks in advance.

ii
come on guys..not a single replay!!!!

is your device rooted? and please check what extension your device supports. i think most device supports ext4

sadler123 said:
hi every one..
i have a problem with my samsung 32g class 10 sd card , i wanted to make a second partition using mini tool, i chose ext2 as a second partition and when i opened link2sd app it asked me to chose the file system of the second partition , again i chose ext2 , it asked me to reboot the device. i rebooted it and when i opened link2sd the same message that asked me to chose the file system of the second partition appeared again and when i chose ext2 this message appeared: "mount script cannot be created. mount invalid argument"
i returned to mini tool and tried both ext3 ext4 with no success. and when i tried fat32 as a second partition it created but when i try to link any app on link2sd it fails to link it.
plz can any one tell me what should I do.
thanks in advance.
Click to expand...
Click to collapse
try making partion ext3 or ext 4
hit thanks if helped <<<<<

may be you missed somethink on sd partition step
those can help you i think http://forum.xda-developers.com/showthread.php?t=1432459

snx413 said:
may be you missed somethink on sd partition step
those can help you i think http://forum.xda-developers.com/showthread.php?t=1432459
Click to expand...
Click to collapse
MY DEVICE IS ROOTED,
I have tried these steps but didn't work on my 32g sd, I tried the same steps befor on a 2g & 4g & 16g sd cards and it worked. but on 32g It didnt work. I don't know why:'( ..plz heeeeeelp!

it seems link2sd work with 32gb so i dont know why not taking your if you did all well
try this may be it will work
http://forum.xda-developers.com/showpost.php?p=37337196&postcount=2

[Q] How to correctly partition 64GB SD card for use in Link2SD?

Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".

SonyXperiaz1s said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD

LS.xD said:
Its pretty simple (at least I hope so):
Partition wizard is fine for preparing your sdcard. Put the sdcard into your cardreader (not the phone!) and delete all existing partitions from the card. Then create one "primary partition" formatted as "fat32". Once done resize the partition meant that you decrease it by the amount of space you need for your EXT4 partition. in the way that the unallocated space (e.g. 1024MB) is behind the Fat32 partition. Then create a "EXT4" partition in the empty space. This partition must also be a PRIMARY partition. or Link2SD will NOT work.
Put the sdcard into your phone and install Link2SD
Click to expand...
Click to collapse
Ah man, I can't tell you how happy I am that someone (you!) actually answered me about this, I've been going everywhere on XDA today. And no worries, I've been using a cardreader, leaving it in the phone just sounds like asking for trouble. And yup, tried that already. Just to repeat back: I made the card partitioned to FAT32 first. Then, after that, I resized it to free up 1024MB. For the first attempt with this method, I tried EXT2 because I wasn't certain if my kernel supported EXT4. And I made sure that the EXT2 partition was behind the FAT32 one. They were both made primary. I made sure my phone was off, and after Minitool did its magic and finished up I put the card into the phone, and rebooted. I launched Link2SD (after clearing its data first, so it would act as a fresh install), and got the onscreen prompt, and selected EXT2. And boom, once again was the annoying mount script error. I tried again, wiping the card and doing everything over identically, except trying it with EXT4 (because why not, eh?) and selecting EXT4 when Link2SD prompted. Same error. I would give it a go (with a smaller card) in my Sony Xperia Z1s, but I thought I read somewhere that Link2SD and Sony doesn't play nicely with each other..? Mainly, I would only want to try that to rule out that it's not user error, but rather an issue with the device. For that matter, I've also got an old Samsung Galaxy Proclaim on 2.3.6 that is also rooted. Perhaps if I'm feeling adventurous, I'll see if I can get it working there. Unrelated side note: How strange that my old Proclaim can read 64gig cards, but my Xperia freaks out with anything above 32! :laugh:

Alright, heres an update for this thread.
The mount script is successful for my Samsung Galaxy Proclaim, but is not on my Huawei Ascend Mate 2, even when the process is done identically.
Wondering why Link2SD seems to hate my HAM2 so much.

Bump

I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.

I dont understand what you did here. May you explain please.
regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
I didnt really get what the steps where to partition my sd card. Like you i have a cheap/no brand 64 Gb Micro Sd card and im unsuccessfull with partitioning it. May you please help me. And in advance Thank You :good:

First let me state that my initial SD card was a Chinese 64GB "fake". Check if yours is also one with RMPrepUSB. Fakes report themselves as having 32GB or 64GB capacity whereas, in reality, they only have a fraction of the reported capacity.
I then purchased Silicon Power SD cards with 32GB and 64GB capacity. I then followed the procedure mentioned above and everything works just fine.

You are brilliant!
I have been having the exact same problem and have spent hours pulling my hair out trying to overcome this issue. Your fix was brilliant as so far it seems to have solved the problem!
One note, I was trying many different methods of partitioning and formatting. This method WILL NOT work with the Aparted app. Mini Tool was the way to go.
Thank You!!!

OK - Here's the thing...
OK, I did this and even posted how it finally worked and got rid of the "mount script error." However, it now seems that because the fat32 partition is now third in line, it looks like Link2SD is now trying to save all the data on the ext4 partition and not the fat32 partition.
When I do the "Link to SD" operation, it seems like it's putting everything on the second partition which is the ext4, but I don't see a change in the space used on the fat32. Am I missing something...?

Maybe the device can't support ext2...
Hi, I got similar problem with you. I've also tried to do partition in reverse order, swap first, then ext2, then fat32. It didn't work. However, when I select repair for the ext2 in Aparted, it said
The super block cannot be read or does not describe the correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the super block is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b8193 <device>
Click to expand...
Click to collapse
So now I'm looking for ext2.ko for Xiaomi Redmi Note but haven't found it anywhere.

regli said:
I've struggled with my cheap/no brand 64GB SD card now for days but I finally succeeded. Hopefully this works over the long haul. We will see.
I have an L34C with very limited internal memory which is why link2sd became essential. So I purchased a 64GB micro SD card through eBay for less than $8..00.
At first I tried to follow the various guides to partition the card using either Minitools/Easeus and even AParted on the phone. Every time the second partition (ext2/4) was added at the end, the partition table got corrupted and then showed file system "other" instead of ext2.
Finally I decided to try the GParted Live CD under Windows 8.1 using VirtualBox (32bit Linux) using the ISO as the boot device. Obviously booting the live CD directly via CDRom/USB works as well but I didn't want to always reboot.
Note that I used SDFormatter to initially low level format and verify that the card was good.
After many trials and errors I got it to work. The key seems to be that all partitions need to start in the first 32GB. This leads to the conclusion that the large fat32 partition needs to be last, before any desired SD card overprovisioning.
As link2sd insists that the ext2/ext4 partition is the second partition, I created a small 32MB Linux swap partition first. I then added a 6GB ext2 Apps partition directly followed by a 48GB fat32 Data partition.. The remainder is unallocated for overprovisioning.
I finally marked the fat32 partition "active" by setting the boot flag.
Before inserting the card, I cleared the link2sd cache and data and then turned the phone off.
Note that in my case link2sd, after the initial reboot, preferred the ext4 check mark for the ext2 partition.
I hope this helps somebody.
Click to expand...
Click to collapse
Will your method works on a 128gb sd card?

I was doing this in fact today, after reading this blog. I was having a helluva time because my Sophone i6 Plus has no regular Settings app, it's laid out like an iPhone Prefs app. The settings I needed are usually under "Storage" in a regular settings app. I was able to repartition my 32gb card on-device with aParted, but I could NOT get Links2SD to detect it, even after setting up the 2nd ext4 partition.
Mainly, after setting up the partitions in aParted, you have to switch your main write disk to internal before rebooting, else Link2SD will spit out whatever you have done. After the device reboots, the main write disk will be set to your first SD partition. After that you should be able to start Links2SD and it will prompt to set up your ext4. Then, Apps2SD will stop give you the message that it can't find the 2nd partition. Scroll down to the bottom of the blog and then the bottom where the comments start or use this link, my response should be visible. It's just a question of doing things in a specific order.
One thing that is mentioned in the tutorial is that for large cards, you should not use Fat32 for the main partition, but ext2 instead.

I've been trading a few emails with Vicki the creator of apps2SD. The best way to set this up is to link the user apps to the SD card but keep the data, the internal data on the internal partition. She said you can put the external data on the SD card but I kept both on internal and everything runs great now.

Great!! This worked perfectly for Link2SD. But now the FAT32 3rd partition isn't showing up in any of the file explorer, backup, etc. apps. What did I miss or still need to do? Thx.

Still lost
Okay I might be a complete dummy but I'm still not understanding or maybe I know it's just not working for me if you could tell me I'll maybe put a picture of the partitioning using minitool from left to right size of the first primary partition size of the second primary partition size of swap file size of any damn thing for that matter it seems you guys tried to explain or try to help but you explain it in a matter that only makes sense to somebody who does nothing but this I'm a old slow and it's stupid truck driver but I would really like to get my SD card working so I can have more storage I do like to play on these things please help

zombunny said:
Alright, I'm having issues with Link2SD. Many others are as well, from the results that came up in a google search. Seems each "solution" is different for multiple people, and I'm getting a lot of contradictions.
I own a Huawei Ascend Mate 2 (Mt3L03 variant) on 4.3, rooted and running stock, kernel version 3.4.0-g1fcc1aa, bootloader unlocked via a code from Huawei themselves. I've tried AParted and Minitool Partition Wizard. Some people say "Use the Windows partitioning software!" and some people say "The chances of errors with Windows is higher, partition it on your Android!"
I've been at this for several hours, over and over, reading countless threads, trying various methods and settings. I tried creating the ext2 partition first a few times, just for funsies, but no luck there. So I've been mainly doing what I assume is correct, partitioning FAT32 first, then ext2. Or ext3. Or ext4. I've been through it all. I've partitioned ext2 (and others) as quite large, up to 48000mbs. I've partitioned it quite small, down to 800mbs. I've added swap. I've done it without swap. I've left empty space. I've filled the whole card. I've partitioned only FAT32 (or ext2, or others) and left the rest blank. I've created 2 FAT32/FAT16 partitions. I've used Link2SD as a user app. I've used Link2SD as a system app. I've rebooted again and again and again and again and AGAIN. I've selected the file system of my sd card's second partition as ext2, ext3, ext4, FAT32/FAT16, and f2fs (tested ALL on EVERY attempt, just to be certain). But after everything is said and done, no matter how certain I am that I finally got it right..... every stinking time it comes back with "Mount script error // Mount script cannot be created. mount: Invalid argument". Good lord I am ready to tear my hair out with this thing! What on earth am I doing wrong? Does it have anything to do with /dev/block/mmcblk1p2 ? I've also tried GL to SD, DS App2SD, and App2SD, but ultimately I'm not satisfied with any of those. I just tried this: http://techtriosonline.com/2014/11/p...-minitool.html Followed it EXACTLY. Still the same issue.
Also tried with AParted. Annnnd still the same issue. I should also note that in the configuration, I've attempted to changed /dev/block/mmcblk1 to dev/block/mmcblk1p2, and I get the warning "Detected internal device memory! To complish the new DDR of google, AParted can't work with internal partitions or gpt table types. One version with no limits will be maintained in the Aparted web site".
Click to expand...
Click to collapse
Hi sorry sorry would you mind doing a tutorial on YouTube please this would be most helpful. Thank you in advance.

[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.

Partition 64GB microsd card to 2 x 32GB FAT32

Hi guys,
I want to partition my 64GB (I know, 59GB actually) microsd card into 2 x 32GB FAT32 partitions. I've tried to do it in windows, using MiniTool Partiton Wizard like I did with other microsd cards until now, but without success: the tool creates two partitions but the 2nd one is not usable (it does not have assigned a letter); any attempts to correct this were futile.
Can this issue be fixed somehow? If yes, how?

Old Jimbo said:
Hi guys,
I want to partition my 64GB (I know, 59GB actually) microsd card into 2 x 32GB FAT32 partitions. I've tried to do it in windows, using MiniTool Partiton Wizard like I did with other microsd cards until now, but without success: the tool creates two partitions but the 2nd one is not usable (it does not have assigned a letter); any attemptions to correct this were futile.
Can this issue be fixed somehow? If yes, how?
Click to expand...
Click to collapse
Start over, get it back to one unallocated partition, then use the Aparted app from play store.
Or you can try this
smallbusiness.chron.com/partition-sd-card-android-57286.html

Thanks for your reply @Droidriven!
I've managed to create those partitions: sdcard1 and sdext2, both FAT32 and having 29.5GB each. First partition (sdcard1) is working flawless: access speed, read, write. The 2nd one...
The 2nd one (sdext2) has an issue - I cannot create files (.txt), in root or in other subfolders. However, I can access it, move data to it from the other partition or from the internal sdcard and I can create folders and subfolders. In android's settings->storage menu, my external sdcard is shown as it has only 29.5GB (out of 59GB) but nothing about partitions.
Is this a permission issue (platform.xml)? Can it be fixed?

Old Jimbo said:
Thanks for your reply @Droidriven!
I've managed to create those partitions: sdcard1 and sdext2, both FAT32 and having 29.5GB each. First partition (sdcard1) is working flawless: access speed, read, write. The 2nd one...
The 2nd one (sdext2) has an issue - I cannot create files (.txt), in root or in other subfolders. However, I can access it, move data to it from the other partition or from the internal sdcard and I can create folders and subfolders. In android's settings->storage menu, my external sdcard is shown as it has only 29.5GB (out of 59GB) but nothing about partitions.
Is this a permission issue (platform.xml)? Can it be fixed?
Click to expand...
Click to collapse
I don't know what your issue is, maybe because one partition is the primary partition. Did you choose all the same options when you set the second partition?
What android version are you using? Lollipop and Marshmallow do have permission configurations that are a pain, especially concerning extsd permissions.
I'll see what I can find, can't promise I'll find you an answer though.

The partitions' settings are identical, with the sole exception that one has to be the primary one. The microsd is new and tested with a few software programs to be sure it's not a fake (it's not).
I'm using AOSP 5.1.1 and yes, I believe there is a L permission issue.
Don't worry a bit regarding this issue. If you or someone else will find the solution, it'll be great, if not, life goes on.
Thanks anyway for taking your time!

Droidriven said:
Start over, get it back to one unallocated partition, then use the Aparted app from play store.
Or you can try this
Click to expand...
Click to collapse
How exactly do I get is back to one unallocated partition? That will solve all my problems right now

Database Info

welcome