Like always make sure you have a apps to sd rom. I would recomned haykuros 5.0.2 G r3 build with apps to sd.
I am not going to cover how to do this here as there is already alot of tutorials explaining this already.
First you should use a card reader and your favorite partioning program to shrink the fat32 partion and make a ext2 partition I would recomend atleast 100 mb. I used acronis disk director suite to make partition. Paragon or any other disk management program would work.
Once completed go download this www.tauruspc.net/scripts.zip
Extract the two scripts to your sdcard and then put back in phone.
Forgot to mention. These scripts move the data and dalvik-cache just FYI
Per other threads says sometime people have problems. But I have ran these on 5 devices with 3 different roms with no issues.
If this is the first time you are putting on apps to sdcard or that build
Download terminal from market and use these two commands
su
sh /sdcard/appstosd.sh
Once that is done reboot phone to recovery console by home and power button to turn on and then apt x
you should get a prompt then and use these two commands
mount sdcard
sh /sdcard/appstosd2.sh
If all goes well phone should restart and when if backup and running enjoy having all apps on sd and a permanent 73 mb free on the phone.
After performing these steps my G1 hangs on the "T-Mobile G1" boot screen.
What software are you running. And you need have apps to sd first with a formated memory card with an ext2 part. Because if you don't have formated card will not work. When you ran script did you get any errors?
script name
hello
the script down load as appstosd1.sh and appstosd2.sh and your post says the 1st one is appstosd.sh
I just rebooted the phone on the 2nd part, i hope this works :/
ive tried like 5 or 6 different ways and thus far none are working
[email protected]
If it works great but my advice guys if it ain't broke don't fix it, its already easy enough with all the tutorials out there.
Why not just use this app:
http://forum.xda-developers.com/showthread.php?t=504451
Install the APK and run the app. How much easier can you get? (Yes you still have to format your card but thats easy.
speoples20 said:
Why not just use this app:
http://forum.xda-developers.com/showthread.php?t=504451
Install the APK and run the app. How much easier can you get? (Yes you still have to format your card but thats easy.
Click to expand...
Click to collapse
That APK app didnt work for me. this is just another option for those who other ways arent working i think.
M9x3mos said:
What software are you running. And you need have apps to sd first with a formated memory card with an ext2 part. Because if you don't have formated card will not work. When you ran script did you get any errors?
Click to expand...
Click to collapse
I am running 5.0.2G-A2SD, I have the sd-card formatted properly.. oh well, the I just followed the other tutorials out there and it worked flawlessly.
EDIT: Okay so I tried this again for the sake of testing, and I can confirm that it works. I guess I did something wrong the first time around.
quick question, do you have to leave the scripts on the sd card or can you take them off when your thru?
bleulady82 said:
quick question, do you have to leave the scripts on the sd card or can you take them off when your thru?
Click to expand...
Click to collapse
You can take them off.. they are just scripts to install the apps to sd. I can also confirm 73MB internal memory.. thank you for these wonderful scripts OP
EDIT: Hmm.. my browser does not seem to work anymore.
i'm getting an error "the process com.google.process.gapps has stopped unexpectedly."
also, tried a reboot and it hung on android screen for ever. did a wipe and had to re-do the scripts for appstosd, still receieving the error above.
Yeah I'm getting force close for anything I click on in the notification bar.
Ok can someone walk me through partitioning my sd card? I have Paragon Partition Manager 9 Pro, and when I delete the partition on my sd, it wont let me create a new one, and it always goes back to saying the whole card is partitioned as an FAT32 when it jus said unallocated
Thanks man. Worked great. Hopefullly I don't run into any future problems.
AsaSpades said:
Ok can someone walk me through partitioning my sd card? I have Paragon Partition Manager 9 Pro, and when I delete the partition on my sd, it wont let me create a new one, and it always goes back to saying the whole card is partitioned as an FAT32 when it jus said unallocated
Click to expand...
Click to collapse
I don't have the link offhand but if you go over to androidcommunity I think you can do a search for a tutorial on how to use Paragon. Good luck.
i think you forgot to mention that a class 6 card is needed to move data/data over to the sd card
im using a class 4 card and when i moved data/data over to my sd card my phone would lock up without me doing anytihng. within 2 seconds of seeing the lock screen it would lag and then force close constantly.
i tried to move it numerous times. no luck
if u have a class 2 card dont even try moving apps to sd
and if u have a class 4 moving everything except data/data and dalvik-cache will be fine. ive moved my dalvik-cache over to my sd card and not that many problems. the ocasional force close but w/e
summary :-D
class 6 = only for moving everything over
class 4 = everything except data/data and dalvik cache
class 2 = buy a class 4 or class 6 card
I used the recovery partition to create FAT32, ext2, and swap partitions on my sd card.
1) What size does it make each of these partitions?
2) What is each used for?
3) When loading the MoDaCo update.zip (and rebooting after first boot) after creating these partitions, what does it do with each of them? My free space on each seems to change, and I think it's loading some apps to the SD card? But not others?
4) How do you see how much space remains on the fat32 and ext2 partitions? Which one is shown in the SD card info settings page, and which one is used for USB mass storage mode? Neither seems to change much even after I install a bunch of >1MB apps.
Thanks for any help.
Also, what's taking up all my internal phone space? If the update.zip moved apps to the SD card, why do I only have 50 MB left of internal space?
jonnythan said:
I used the recovery partition to create FAT32, ext2, and swap partitions on my sd card.
1) What size does it make each of these partitions?
2) What is each used for?
3) When loading the MoDaCo update.zip (and rebooting after first boot) after creating these partitions, what does it do with each of them? My free space on each seems to change, and I think it's loading some apps to the SD card? But not others?
4) How do you see how much space remains on the fat32 and ext2 partitions? Which one is shown in the SD card info settings page, and which one is used for USB mass storage mode? Neither seems to change much even after I install a bunch of >1MB apps.
Thanks for any help.
Click to expand...
Click to collapse
32 mb swap, 500mb ext2 rest fat32
swap is for linux swap if its used in the rom, ext2 is for your apps, and fat32 is for your storage
yes it loads all of your /data/app and /data/app-private apps on your sd card, your /system/app stays there
you can do a df -h under adb to see your free space
jonnythan said:
I used the recovery partition to create FAT32, ext2, and swap partitions on my sd card.
1) What size does it make each of these partitions?
Click to expand...
Click to collapse
I believe it makes a 32MB Swap partiton, a 500 MB Ext2 partition and the rest fat32.
jonnythan said:
2) What is each used for?
Click to expand...
Click to collapse
The Fat32 is normal files like music, pictures, etc. The ext2 is used for apps2sd. Don't worry, 500MB is more than enough for this. The swap is used for bakcground applications so they run better without slowing the phone down as much.
jonnythan said:
3) When loading the MoDaCo update.zip (and rebooting after first boot) after creating these partitions, what does it do with each of them? My free space on each seems to change, and I think it's loading some apps to the SD card? But not others?
Click to expand...
Click to collapse
The Fat32 it shouldnt do anything. Obviously you will have less space because the other partitions are taking some of it's space. It loads the apps onto your ext2 partition but not all of them. System apps such as the calculator, browser, phone, etc stay on the system partition because it's faster.
jonnythan said:
4) How do you see how much space remains on the fat32 and ext2 partitions? Which one is shown in the SD card info settings page, and which one is used for USB mass storage mode? Neither seems to change much even after I install a bunch of >1MB apps.
Thanks for any help.
Click to expand...
Click to collapse
Do you have Windows, Linux or Mac. I don't know about Mac but I know Linux can view ext partitions natively (obviously, it's the native filesystem). For Windows you might be able to load the disk management application but if that doesnt show it you need a partitioning application or any other application that can read ext partitions off an sdcard. Don't know any off hand except paragon partitioning manager 9.0 (8.0 never seemed to work with my sd cards)
jonnythan said:
Also, what's taking up all my internal phone space? If the update.zip moved apps to the SD card, why do I only have 50 MB left of internal space?
Click to expand...
Click to collapse
See the above explanation.
nelson8403 said:
32 mb swap, 500mb ext2 rest fat32
swap is for linux swap if its used in the rom, ext2 is for your apps, and fat32 is for your storage
yes it loads all of your /data/app and /data/app-private apps on your sd card, your /system/app stays there
you can do a df -h under adb to see your free space
Click to expand...
Click to collapse
That answers my questions, thank you.
I found another though. I unmounted my SD card via Settings to see if the apps would fail to work in an effort to try to figure out if they were actually installed there. Predictably, they failed to work, but the system didn't pick the card back up after I reinserted it. So I rebooted the phone with the SD card in.
Then everything died. The apps didn't come back, but the phone still had them listed and tried to launch them, resulting in force-closes. An ext2 repair didn't fix it, so I just went back to my last Nandroid backup and reapplied update.zip.
I learned that this is a Bad Thing to do, but I'm wondering if this was a fluke or is it generally inadvisable to unmount the SD card for this reason?
im a noob to the whole android thing.but how do i partition the sd card and create ext2?????
jonnythan said:
I learned that this is a Bad Thing to do, but I'm wondering if this was a fluke or is it generally inadvisable to unmount the SD card for this reason?
Click to expand...
Click to collapse
Since this is a simple symlink, if you reboot the phone without the target of the symlink being there, and the phone tries to use it...
The results are left as an exercise for the reader.
Now for anyone who asks why it isn't smart enough not to break... that's like asking why your car doesn't run if you take half the spak plugs out.
posguy99 said:
Since this is a simple symlink, if you reboot the phone without the target of the symlink being there, and the phone tries to use it...
The results are left as an exercise for the reader.
Now for anyone who asks why it isn't smart enough not to break... that's like asking why your car doesn't run if you take half the spak plugs out.
Click to expand...
Click to collapse
Ah, but I'm asking why it still doesn't work once you put the spark plugs back in
It's not a big deal, I certainly learned not to do it.
jonnythan said:
Ah, but I'm asking why it still doesn't work once you put the spark plugs back in
It's not a big deal, I certainly learned not to do it.
Click to expand...
Click to collapse
Because booting the phone with it thinking the app was installed but it not able to find it trashed other data structures.
BTW, people trying to do stuff with the SD card removed after putting the apps on the SD card is probably one of the main reasons it currently is root only.
The OS needs to be modified to handle removable app storage gracefully (not something that happens in a standard phone.)
So should you format the card prior to flashing Modaco's ROM so the system knows to install all the apps to the ex2 partition. Or can you format the card AFTER you have already flashed Modaco's ROM and still have the apps automatically install on ext2 partition? I only ask cuz I formatted after flashing the ROM and wanna make sure it's installing it on the ext2.
I formatted mine afterwards and it moved all my apps over to the sd card automatically.
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.