Hello guys. I've been struggling with this for 3 days now.
The thing is that I need to have an SD with 2 partitions for internal storage on android. The wierd thing is, no matter what procedure I take, the second partition cannot be formated. I can create the partition, but I when I format it it ends up with the file system "Other".
I've tried with A LOT of procedures, a lot of programs, I read a lot of guides, and nothing works.
This is all the info I can provide:
First partition works well in every case, I can read and write in it.
If second partition is Primary, file system is ALWAYS "Other" and NO free space left (all space marked as used), but if partition is logical, it does not even create it (updates as unallocated after commitment, as if nothing ever happened).
That "Other" partition is not recognized by nothing, and there is no way I can explore it.
I've tried in Windows 7 64 bits, Linux GParted Environment, Android 6.0 Marshmallow and Android 4.4 Kitkat.
I've tried in 3 devices: A PC, a Notebook and Moto E android with stock rom and CM 13.
I have 2 MicroSD, Kingston 16 GB Class 4 and Kingston 16 GB Class 10. All the procedures where repeated in both SD cards, so I discard the SD being broken.
I've used MiniTool Partition Wizzard, Acronis Disk Director Suite, EaseUS Partition Master and Paragon Hard Disk Manager on windows and AParted, Apps2SD: All in one tool and Parted4Android in Android (As well as GParted).
Tried both MBR and GTP. Same issue.
Tried FAT16, FAT32, NTFS, ext2, ext3 and ext4 in both first and second partition in MBR and GTP, primary and logical (ALL combinations, yes, a LOOOOT of formatting :3)
If third, fourth (and so on) partitions are created, the same as second partition happens.
I can succesfully create a second partition in a USB PenDrive.
Tried for example this: Created 2 partitions as FAT32, as always second partition marked as "Other", entered the first partition from windows, created a file. After that I switched the partitions with wasp. Once the other partition was active, when I tried to enter windows said "Drive X has no format, want to format?" Yes "Could not format X".
So, WHAT in the world am I supposed to do? D:
Thanks in advance guys :3 And sorry for my bad english.
UNATCOPres said:
Hello guys. I've been struggling with this for 3 days now.
The thing is that I need to have an SD with 2 partitions for internal storage on android. The wierd thing is, no matter what procedure I take, the second partition cannot be formated. I can create the partition, but I when I format it it ends up with the file system "Other".
I've tried with A LOT of procedures, a lot of programs, I read a lot of guides, and nothing works.
This is all the info I can provide:
First partition works well in every case, I can read and write in it.
If second partition is Primary, file system is ALWAYS "Other" and NO free space left (all space marked as used), but if partition is logical, it does not even create it (updates as unallocated after commitment, as if nothing ever happened).
That "Other" partition is not recognized by nothing, and there is no way I can explore it.
I've tried in Windows 7 64 bits, Linux GParted Environment, Android 6.0 Marshmallow and Android 4.4 Kitkat.
I've tried in 3 devices: A PC, a Notebook and Moto E android with stock rom and CM 13.
I have 2 MicroSD, Kingston 16 GB Class 4 and Kingston 16 GB Class 10. All the procedures where repeated in both SD cards, so I discard the SD being broken.
I've used MiniTool Partition Wizzard, Acronis Disk Director Suite, EaseUS Partition Master and Paragon Hard Disk Manager on windows and AParted, Apps2SD: All in one tool and Parted4Android in Android (As well as GParted).
Tried both MBR and GTP. Same issue.
Tried FAT16, FAT32, NTFS, ext2, ext3 and ext4 in both first and second partition in MBR and GTP, primary and logical (ALL combinations, yes, a LOOOOT of formatting :3)
If third, fourth (and so on) partitions are created, the same as second partition happens.
I can succesfully create a second partition in a USB PenDrive.
Tried for example this: Created 2 partitions as FAT32, as always second partition marked as "Other", entered the first partition from windows, created a file. After that I switched the partitions with wasp. Once the other partition was active, when I tried to enter windows said "Drive X has no format, want to format?" Yes "Could not format X".
So, WHAT in the world am I supposed to do? D:
Thanks in advance guys :3 And sorry for my bad english.
Click to expand...
Click to collapse
HI.BRO
GO.TO. CM13 THEN Reboot TO ClockworkMOD Recovery THEN CHOOSE Advanced THEN.Choose PARTITION SD CARD
Choose Partition SIZE
THEN Choose SWAP SIZE(SELECT 0 IF.U WANT TO.LEAVE SWAP)
GIVE A THANKS.IF I.HELPED U
Related
Hi,
I have sucessfully moved my apps and caches to my 1.6gb ext2 partiton on my 8gb sd card.
I would like to back up the ext2 partition in case my sdcard fails.
How do I do this in windows xp?
Thanks
I'd love to find out how to do something similar. I just got an 8 GB card that I'd like to replace my 2 GB card with, basically, I'd like to clone the whole thing over.
Anyone have any ideas? I can do XP or Linux, just curious what software would be able to do the best job of replicating the card from one to the other.
Attach the card to your computer with an adapter (not the phone as it will be mounted by android). Download and install ext2ifs from here. You will now be able to see the files on the ext2 partition and can copy/paste them to where ever you would like.
Thanks, but I've had no luck with ext2ifs and memory cards. They even address it in their troubleshooting section:
I have a device with a removable media, for example a USB memory stick, a Compact Flash Card, a magneto-optical drive etc., which has a partitioned format and has more than one partition. When I insert that media, a drive letter appears for the first partition, but not for all the remaining partitions of the media. When I open "IFS Drives" of the control panel, the considered device appears as a hard disk drive, but there is no partitioning scheme shown for it. How can I create drive letters for the remaining partitions of that removable media? (USB hard disk drives are not affected.)
There is an unsatisfactory answer only: it is not possible.
Windows creates (and deletes) all the drive letters for pure removable devices or removable medias itself. Because the Ext2 IFS software need not to create them, it intentionally does not show any partition scheme for that drive.
Windows creates a drive letter for the first partition of the considered media, but not for the remaining ones. (Windows NT4, 2000 and even XP behave the same way in that regard).
You will run into the same problem if you have a removable media partitioned with two partitions of the FAT type on a computer, which has not installed the Ext2 IFS software! So there is one straight advice only: do not use removable media with more than one partition with Windows.
I'm guessing (someone else could correct if wrong) that if I were to just do the basic copy from one card to another - that would suffice?
If I just took the card, created two partitions (FAT32 and EXT2FS) on the larger card, then copied over all the files in both - that would work just fine?
Strange, I've never experienced any issues with ext2ifs, but yes a simple copy paste of both partitions has been all i needed. Just make sure to copy any hidden files as well.
Can we back it up using Ubuntu Live CD and just upload them to a new sd cards ext2 partition?
yes, but you would need multiple card readers.
andonnguyen said:
yes, but you would need multiple card readers.
Click to expand...
Click to collapse
Why can't you save it to the hard drive, replace the sd card, access the ext2 partition and upload the files that you backed up?
Although I'm not very familiar with Ubuntu, when I tried it last time it didn't even allow me to have access to the app and app-private folders within the partition.
What do I need to do to be able to back it up to the hard drive so I can try to upload it to another SD?
Hi,
Thanks for the suggestion.
But when I installed the driver, I can still see just the fat32 partition not the ext2 partition.
I am using a sdhc usb card reader so it is not connected to the g1.
It is like the ext2 partition does not exist through windows xp.
But when I put the card back in the g1 the files are taking up space through ternminal emulator. So the ext2 partiton does exist but still not accessable through windows.
Any other ideas?
jsunkist146 said:
Attach the card to your computer with an adapter (not the phone as it will be mounted by android). Download and install ext2ifs from here. You will now be able to see the files on the ext2 partition and can copy/paste them to where ever you would like.
Click to expand...
Click to collapse
bestwebs said:
Hi,
Thanks for the suggestion.
But when I installed the driver, I can still see just the fat32 partition not the ext2 partition.
I am using a sdhc usb card reader so it is not connected to the g1.
It is like the ext2 partition does not exist through windows xp.
But when I put the card back in the g1 the files are taking up space through ternminal emulator. So the ext2 partiton does exist but still not accessable through windows.
Any other ideas?
Click to expand...
Click to collapse
what comes up when you use
"busybox df -h" in the terminal emulator?
make sure you see something like "/dev/mmcblk0p2 (partition size) (used) (available) (used %) "/system/sd"
If not then that's the problem.
Hi,
In my phone , I do have that ext2 line /dev/mmcblk0p2
size 1.4gb - used 49 meg - free 1.3 gb
sdcard line /dev/mmcblk0p1
size 6.2 gb - used 5.2gb - free 981 meg
Thanks for the reply.
Binary100100 said:
what comes up when you use
"busybox df -h" in the terminal emulator?
make sure you see something like "/dev/mmcblk0p2 (partition size) (used) (available) (used %) "/system/sd"
If not then that's the problem.
Click to expand...
Click to collapse
If you're on Linux it is trivial to get the files off, if you'd like to make an exact image you can use the dd command. I suggest grabbing a live CD, as it will be a much easier process than making windows see ext partitions.
crater said:
If you're on Linux it is trivial to get the files off, if you'd like to make an exact image you can use the dd command. I suggest grabbing a live CD, as it will be a much easier process than making windows see ext partitions.
Click to expand...
Click to collapse
I have the Live CD, but can you elaborate on the "dd command" exactly. I'm a Linux noob and wouldn't mind backing up the partition. Last time I tried, I couldn't even get permissions to open the files no less copy them.
Thanks.
Insert the two SD cards into USB SDHC card readers. Launch the free MiniTool Partition Wizard program. Copy the ext2 partition you want to transfer on the first SD card to an unallocated area on the second SD card. MiniTool Partition Wizard under Windows does "see" multiple partitions on a USB drive even though Windows doesn't assign letters to those drives and they are invisible in Windows Explorer.
To increase the size of the ext2 partition on either SD card, use the Linux program GParted. Boot up with the GParted Live CD/USB iso file. Run GParted to resize the ext2 partition. (MiniTool Partition Wizard can move but not resize an ext2 partition.)
I figured instead partition to ext2 first then revert to ext3 with some of the Roms, why don't we just partition the sd card to ex3t with Acronis Disk Director Suite.
It's simple and easy:
1. plug in sd card to the computer and open Acronis Disk Director Suite
2. click on the sd card drive and under wizard menu click on create partition
3. choose free space of the existing partitions to create first fat 32 partition
4. click next, choose the sd card drive
5. NEXT, and choose the size of your regular fat 32,( i have a 8bg so i put 6.5gb here) and choose fat 32
NOW creating ext3 partition:
6. under wizard menu again, choose create partition (sd card drive)
7. choose free space of the existing partitions
8. click next, choose the drive
9. click next, choose the size, again i put 1.5gb to put all my apps
10. NOW here, i choose ex3t under the type menu.
11. after all, just simply click to create the partitions and you're done.
Now you should have one fat 32 and one ext3
After all, just run the app2sd script under sdk, again it's a very easy step too, if you need me to post it, i will.
i just tested it myself, it worked, again it's your own risk , i found it so much easier to do it this way.
my knowledge of linux is very limited... so I'm gonna have to ask... how is ex3t different from ext3?
I get the impression xnycen means ext2 and ext3 but is writing it wrongly for some reason.
ebadevil said:
my knowledge of linux is very limited... so I'm gonna have to ask... how is ex3t different from ext3?
Click to expand...
Click to collapse
I don't think there is anything called EXT3T, it's EXT3.
Anyways there are too many threads about this and you can do it with GParted or Partition Manager anyways. I know why people are so complainy around here, it's because no one reads and everyone thinks they're the first to ask a question or post a new idea.
dont use acronis... ive lost 4 PC's to that beast, it never works properly. never writes anything correctly. and if you are using it to create formats and partitions... im going to have to say you have had amazing luck.
and above all, never use the OS selector.
hi,
i made partitions by using clockwork 3.0, i select 1 gb when it ask first, and 512 mb for swap. However, i dont know if this 1 gb partition is ext2 or ext3 or somehing else...
how can i see my sd card partitions...?
thanks....
polatkanfatih said:
hi,
i made partitions by using clockwork 3.0, i select 1 gb when it ask first, and 512 mb for swap. However, i dont know if this 1 gb partition is ext2 or ext3 or somehing else...
how can i see my sd card partitions...?
thanks....
Click to expand...
Click to collapse
Hi polatkanfatih,
You can't directly access the ext2 partition in Windows. Basically ext2 is a linux partiton. But still there are some 3rd party softwares available in the market which adds ext2 abilities to windows Operating System.
As per what you have written, i understood that you used Clockwork 3.0 for partitioning your SD card.Personally i don't know about clockwire.
Instead i'm using ''MiniTool Partition Wizard Home Edition 5.2'' which you can download for free from the MiniTool website.The software is pretty easy to use.With this software you can see the partitons you have created(including ext2).You can't access the files inside the partion, but you can format any partition using MiniTool.
Hope this helps........
that program doesnt make that work.
i need some adb code or somthing else to see how my sd card partitioned, how many partition are there and their sizes?
have you tried typing
Code:
mount
in terminal emulator or adb shell? That should give you a listing of all mounted partitions...
i made it with 'parted' adb command.
thanks..
i didn't undestand but still reading
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.
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
Hi this is really the solution for creating the 2nd partition for app2sd or link2sd and also the solution for partitioning sdcards larger than 16gb i tried my 16gb with normal partition method and i was mounted at first time but my 32gb and 64gb they just wouldnt mount so this is the solution for it i tested it and it works tested on ICS 4.0.4 and marshmallow 6.0.1
thank you very much for this solution i had been hammering my head for the last 2 months
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
You so totally saved my day!!! There is nothing in the FAQ of Link2SD about this ... OMG
I already tried for weeks ...
THX a lot
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
it works for me as ive been getting the the partition ext2 showed file system "other" instead of ext2 as well, try many ways didnt work and finally got my sd card working now!!! thank you so much!!! :good: but instead of link2sd i used apps2sd as link2sd i still get the mount eror
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.
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.