Hi,
I have a problem with my link2sd application.
Using Mini tool partition wizard I have created second partition of type primary and format type FAT32.
And I have successfully created second partition.
Then I installed link2sd. And app prompt for super user permissions and I clicked allow and checked the box remember.
After that the app prompt for to select second partition type and I selected FAT16/FAT32. Then I am getting an error message mount scripts cannot be created. I tried all format types ( ext2/3/4 & FAT32) and getting same error message.
I am using xperia arc LT15i, rooted, boot loader unlocked.
Using FXP CM10 FXP 138.
I tried with FXP 137/138 and getting the same error.
Can anyone please help me to successfully link second partition.
Thanks in advance.
Format the card in Windows then create the partition with the recoveryARC.img from HERE.
XperienceD said:
Format the card in Windows then create the partition with the recoveryARC.img from HERE.
Click to expand...
Click to collapse
The megaupload links are not working. (Blocked). Can you please elaborate how to do?
When you create the partition, try to format it on EXT2 or EXT3, then go to Link2SD and select the new partition. Link2SD will ask to reboot. If it doesn't ask, reboot the phone and open again Link2SD. It worked for me this way. I'm on stock rom .587 but it should work.
Good luck!
Make sure that both partitions are primary.
Sent from my LT18i using xda app-developers app
karthik1228 said:
Can you please elaborate how to do?
Click to expand...
Click to collapse
Take your pick - recoveryarc.img
pablopablo said:
When you create the partition, try to format it on EXT2 or EXT3, then go to Link2SD and select the new partition. Link2SD will ask to reboot. If it doesn't ask, reboot the phone and open again Link2SD. It worked for me this way. I'm on stock rom .587 but it should work.
Good luck!
Click to expand...
Click to collapse
I did the same thing, but when I am selecting the partition I am getting error message - "mount scripts cannot be created".
XperienceD said:
Take your pick - recoveryarc.img
Click to expand...
Click to collapse
Thanks. can you please tell me the steps how to create.
karthik1228 said:
Thanks. can you please tell me the steps how to create.
Click to expand...
Click to collapse
Run it with fastboot.
Sent from my CM9'd Arc
Is your phone is rooted then flash recovery image with Flash tool. Boot into recovery go to advance do partitions chose your size ( if you have 16g and up) chose 1g and on next screen chose between 32 & 64 ( i chose 64 ) and chose ext3. after that download link2sd and chose ext3 and follow on screen instruction.
Good Luck.
NB to reboot into recovery you have 2 ways either download x-part from the market or turn off your phone, start it and hold menu bottom and you will reboot into recovery mode
If I helped hit Thanks Bootom:good:
karthik1228 said:
I did the same thing, but when I am selecting the partition I am getting error message - "mount scripts cannot be created".
Click to expand...
Click to collapse
Did you install busybox? It might be needed and dont't forget to give superuser permission to link2sd.
I remember I got that error message but link2sd asked for rebooting. after rebooting already worked.
Main reason to not be able to creat script is maybe your SYSTEM memory is full.
Delete something from the system memory (wallpaper or something like this) and Link2SD will make the script and mount 2-nd partition
karthik1228 said:
Hi,
I have a problem with my link2sd application.
Using Mini tool partition wizard I have created second partition of type primary and format type FAT32.
And I have successfully created second partition.
Then I installed link2sd. And app prompt for super user permissions and I clicked allow and checked the box remember.
After that the app prompt for to select second partition type and I selected FAT16/FAT32. Then I am getting an error message mount scripts cannot be created. I tried all format types ( ext2/3/4 & FAT32) and getting same error message.
I am using xperia arc LT15i, rooted, boot loader unlocked.
Using FXP CM10 FXP 138.
I tried with FXP 137/138 and getting the same error.
Can anyone please help me to successfully link second partition.
Thanks in advance.
Click to expand...
Click to collapse
"mount scripts cannot be created" is not an error. It comes because the device is busy . After selecting FAT 32, u have to reboot and open link2sd again, this time it will work
pentium1061 said:
"mount scripts cannot be created" is not an error. It comes because the device is busy . After selecting FAT 32, u have to reboot and open link2sd again, this time it will work
Click to expand...
Click to collapse
can be an error if it doesn't recognize the partition... you have to make it primary in order to work!
wazMe said:
can be an error if it doesn't recognize the partition... you have to make it primary in order to work!
Click to expand...
Click to collapse
EDIT, SOLVED: Found the problem. The System partition was full in CM10 so the boot script creation failed. After removing some unused system apps the boot script creation worked!
Same problem here. Just updated to CM10 FXP148.
Worked fine before with rooted stock ROM and ext2. Now I can't get the boot scripts to work with any type of partition. But link2sd manage to mount an ext4 partition AFTER boot i.e when you open link2sd. That doesn't help though, because link2sd needs the boot scripts for the system to actually find your linked apps...
Has anyone manage to get link2sd to work with CM10?
Is it possible to create the mount scripts manually?
//Moelito
Related
I'm using ClockworkMod Recovery 2.5.0.1 and i've seen a couple of guides where I go into the recovery and do some bits and bobs there to create it, but the only options I seem to get are to mount the sd-ext partition, which fails because it doesn't exist, or to format it.
I'm guessing there is a step beforehand i'm missing?
Thanks
download rom manager from market , open it , then create a ext3 partionion ... done
before you create a partition , backup your sd card!!
y2viks said:
I'm using ClockworkMod Recovery 2.5.0.1 and i've seen a couple of guides where I go into the recovery and do some bits and bobs there to create it, but the only options I seem to get are to mount the sd-ext partition, which fails because it doesn't exist, or to format it.
I'm guessing there is a step beforehand i'm missing?
Thanks
Click to expand...
Click to collapse
I had the same problem.
You can create the partition using the ROM Manager app downloaded from the market as yasars said.
Alternatively, if you want to do it manually, you can format the card on a *nix system. The Gparted Linux app lets you edit the partitions in a nice and simple GUI. Just remember the order of the partitions: first fat32, then about 512 MB of ext2/3/4 (ext4 may not be supported by all ROMs so better to use ext3) and lastly a swap partition of about 32 MB (totally optional). The size of the fat32 partition is whatever is left over after you've allocated the 512 MB for the ext2/3/4 partitions (and the 32 MB for the swap if you decided you wanted it). For instance, for a 2GB card, leaving 512 MB for the ext2/3/4 partition (no swap) leaves us with about 1.5 GB for the fat32 partition. You do the calculations for your card in your head or on paper and use those values in Gparted.
HTH.
Thanks for the help guys
I think i'll just get it up and running using the ROM Manager and if I find the need I'll do a manual version
Foolowing this guide I partitioned my sd card with GParted Live CD.
gianton said:
Foolowing this guide I partitioned my sd card with GParted Live CD.
Click to expand...
Click to collapse
You have no Idea how cool it is for me that my tutorial was useful... ;-)
chrysochire said:
You have no Idea how cool it is for me that my tutorial was useful... ;-)
Click to expand...
Click to collapse
Yes it should be a sticky!
Having a problem when I try to use ROM Manager.
I select the 512 for EXT and 32Mb for Swap and the phone reboots.
It then shows the big triangle with Mr Android next to it until I press some buttons and then I get the recovery screen with the following messages
Finding Update Package....
Opening Update Package....
Verifying Update Package....
E:failed to seek in /cache/update.zip (Invalid Arguement)
E:signature verification failed
Installation Aborted.
I don't have a cache folder on my sd card so i'm guessing it's looking in the internal memory?
Not sure what to do here
BACK-UP sd card before you do this.
For windows users
have clockwork recovery and rom manager on your desire
then format sd in windows.
put it in your desire and go to rom manager.
select Partition SD Card
select your space i used 32 swap 512 ext
than reboot and your sd card has the ext partition.
than put your files back on your sd card and Done
y2viks said:
Having a problem when I try to use ROM Manager.
Click to expand...
Click to collapse
I had the same problem with ROM Manager. My solution was to downgrade ClockworkMod Recovery to v2.5.0.0 (in ROM Manager) and then partition the card. Worked on first try.
When you're done you can upgrade to latest version again if you want.
I don't think you should use a swap partition, so just set it to 0 MB.
Good luck!
Do i just need to find the 2.5.0.0 update.zip file and flash?
going to 2.5.0.0 worked
so now i have the ext partition do I need to do anything for apps to be installed there, or will they install there by default?
Also i've heard that the ext partitions can be 2 3 or 4. I'm presuming higher is better. How do I go about finding what mine is and how can I upgrade it if it need it?
Thanks
chrysochire said:
You have no Idea how cool it is for me that my tutorial was useful... ;-)
Click to expand...
Click to collapse
Hi, I'm also going to give your guide a go. Just one question, do I have to do it with the SD card still in the phone or can i do it with a SD USB adapter?
Thanks,
Joe
I read the tutorial again and you can use an SD adapter, worked a treat. Cheers
y2viks said:
going to 2.5.0.0 worked
so now i have the ext partition do I need to do anything for apps to be installed there, or will they install there by default?
Also i've heard that the ext partitions can be 2 3 or 4. I'm presuming higher is better. How do I go about finding what mine is and how can I upgrade it if it need it?
Thanks
Click to expand...
Click to collapse
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
Code:
su
ls -l /data
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
I'm not sure which format ROM Manager defaults to, but you can always check the type of format used by mounting the card in Linux and using the GParted Linux app (you could use a card reader or use the 'Disk Drive' option in your phone to connect it to the computer). Also, ext3 should be fine for most custom ROMs. In fact, not all ROMs support ext4.
ikkokusenkin said:
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
.
Click to expand...
Click to collapse
- Another quick way is to install quick system info from the Market, it tells you infos about your system, including the use of your a2sd partition.... ;-)
- About ext 2/3/4 I would advise the use of ext3, as ext4 is poorly supported by Roms (even those who pretend seem to have issues...)
cheers
Does the decrease of available internal storage means apps22sd+ is not working? I've partitioned twice and installed seperate 2.2 roms with apps2sd+ included and every time I install more things I see internal storage drop.
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
Click to expand...
Click to collapse
I checked this and it's doing what you said
ikkokusenkin said:
As long as you have an ext2/3/4 partition and the ROM you're flashing has A2SD support (check before you download the ROM), you are not required to do anything more. To check whether A2SD is working once you've flashed your ROM, download the Android Terminal Emulator app from the market and use the following commands
Code:
su
ls -l /data
You should see your app directory pointing to /system/sd/app and app-private pointing to /system/sd/app-private
Click to expand...
Click to collapse
I took the liberty of including this information into my tutorial. I added a reference to you. ;-)
I hope this makes it to Sticky one day... ;-)
bloosteak said:
Does the decrease of available internal storage means apps22sd+ is not working? I've partitioned twice and installed seperate 2.2 roms with apps2sd+ included and every time I install more things I see internal storage drop.
Click to expand...
Click to collapse
Not in itself, no. Those symbolic links mean that A2SD is working fine. However, from what I understand about the theory, even A2SD installs a part of the app into the internal memory. That may explain the drop you see. By the way, how much free memory do you see on your device? I usually have about 140 MB free on my Desire. I read somewhere that if A2SD wasn't working, that figure would be about 90 MB.
chrysochire said:
I took the liberty of including this information into my tutorial. I added a reference to you. ;-)
I hope this makes it to Sticky one day... ;-)
Click to expand...
Click to collapse
Thanks. Although, I can hardly claim to have come up with the idea myself.
ikkokusenkin said:
Not in itself, no. Those symbolic links mean that A2SD is working fine. However, from what I understand about the theory, even A2SD installs a part of the app into the internal memory. That may explain the drop you see. By the way, how much free memory do you see on your device? I usually have about 140 MB free on my Desire. I read somewhere that if A2SD wasn't working, that figure would be about 90 MB.
Click to expand...
Click to collapse
108 free total of 148
I just recently opened spare parts apps where it allowed me to change where apps2sd installs things. By default it was set to automatic and I'm guessing that was causing the problem. I set it to external and tried installing a browser while my disk was mounted and it wouldn't let me do it. Then I set it to charge mode and it installed normally.
Some roms probably default to external while some automatic.
edit: Just installed an app that I previously installed while using "automatic" and it still uses up internal storage instead of A2SD storage. Dunno what's wrong. I am using ext2 partitioned through rom manager.
Hello Guys!
I did Root my desire GSM Hboot 0.93. it came unlocked and is designed to be operated in Europe.
Superuser installed and BusyBox too("Your phone is rooted).
I used Gparted to partition Fat32 ence the same as the tutorial of xda
I tried ext2, 3 and 4. I left as FAT32 as the most compatible with the ROM's.
Yet when I enter the link2sd it asks to select the system partition and i put fat32/fat16, it says "you cannot create the script. not enough memory install.sh inst-sd.sh.
Anyone had this problem?
Someone help me or know a link or how to resolve this situation?
Thanks
Manzatto said:
Hello Guys!
I did Root my desire GSM Hboot 0.93. it came unlocked and is designed to be operated in Europe.
Superuser installed and BusyBox too("Your phone is rooted).
I used Gparted to partition Fat32 ence the same as the tutorial of xda
I tried ext2, 3 and 4. I left as FAT32 as the most compatible with the ROM's.
Yet when I enter the link2sd it asks to select the system partition and i put fat32/fat16, it says "you cannot create the script. not enough memory install.sh inst-sd.sh.
Anyone had this problem?
Someone help me or know a link or how to resolve this situation?
Thanks
Click to expand...
Click to collapse
Haven't used the script but the sys partition is the sd-ext.
paul.c said:
Haven't used the script but the sys partition is the sd-ext.
Click to expand...
Click to collapse
I Don't understand well.
When I start link2sd it opens a window and asks.
"Select the system partition." When I select any items of it displays "error to create the script." When i choose fat32 it show me the message not enough memory.
Do not exist the option-> sd-ext.
I'm noob
Thanks
I have a htc desire stock orange uk, S-OFF, rooted.
With link2sd all I did was use Ubuntu and gparted to partition my 8gb sd card the 2nd partition set at 1024mb and the rest all together both FAT32 as on the market app info it says ext2, ext3 etc etc can only be used with a custom rom.
hope this helps
This has been a life saver went from 17MB free to Nearly 60MB!!!!!
I have the same problem.
partitioned the SD card second partition with FAT32, made it primary but link2sd gives me the same arror as reported by Manzatto.
"mount script cannot be created. :cannot create /system/etc/install-recovery.sh: not enough memory"
thank you.
G.
It's required for you to have first partition fat32 and second one ext (mine is ext3). When it asks point to ext one and that's it.
Hi, I've the same problem. Here is the explanation:
Kierrok said:
Link2SD needs install-recovery.sh or init.d support enabled to mount its partition at boot time. The problem is Samsung GB ROMs don't have it.
You can enable init.d support easily if you cook your ROM. If you can't do it for yourself ask your ROM devel to enable it.
Click to expand...
Click to collapse
It ist impossible to change or create this files, because the rom is mounted readonly. So you need to ask the developer of your custom rom to support link2sd.
It's possible to mount your ext2/3/4 partition manually for link2sd , but every reboot would destroy it.
Greetings Max
I also have the same problem.
I partitioned the SD card second partition with FAT, made it primary but link2sd gives me the same arror:
"mount script cannot be created. :cannot create /system/etc/install-recovery.sh: not enough memory"
Also tried with ext2, ext3 and ext4 and same error.
Currently using this ROM: http://forum.xda-developers.com/showthread.php?t=1200261
Hi,
I have Cyanogenmod 7 on my Desire.
And I'm running Ubuntu 11.04 on my PC.
I copied the contents of my SD Card and the Apps2SD Partition (including hidden files), erased my SD Card and formatted it again (ext3 and FAT32), copied everything back (including hidden files) and now I get a boot loop.
-I used MicroSD>SD Card Adapter>PC
-I can access recovery
-I reduced the size of the ext partition from 1GB to 700MB
-I didn't make a nandroid backup before I did this.
-I changed the label of the ext partition.
-I'm using this for Apps2SD
Is there possibly some sort of temporary files/cache I can delete to make it work?
Thanks
Ano8 said:
Hi,
I have Cyanogenmod 7 on my Desire.
And I'm running Ubuntu 11.04 on my PC.
I copied the contents of my SD Card and the Apps2SD Partition (inclusing hidden files, erased my SD Card and formatted it again (ext3 and FAT32), copied everything back and now I get a boot loop.
-I used MicroSD>SD Card Adapter>PC
-I can access recovery
-I reduced the size of the ext partition from 1GB to 700MB
-I didn't make a nandroid backup before I did this.
-I changed the label of the ext partition.
Is there possibly some sort of temporary files/cache I can delete to make it work?
Thanks
Click to expand...
Click to collapse
The order of the partitions have to be FAT32 followed by the ext3 (and not viceversa)...Is it?
andQlimax said:
The order of the partitions have to be FAT32 followed by the ext3 (and not viceversa)...Is it?
Click to expand...
Click to collapse
They are in that order (unless you mean formatted first?)
The important thing is that the first partition is a fat32, and the second the ext
From the recovery menu try to see if it can mount the ext partition (try just a mount/unmount of the sd-ext to check if the recovery can access the ext) otherwise u can format it from the recovery and then copy back the files from ur pc car reader
U can also try wiping cache and dalvik cache, but don't think will have effects
Otherwise I have no other ideas
andQlimax said:
The important thing is that the first partition is a fat32, and the second the ext
From the recovery menu try to see if it can mount the ext partition (try just a mount/unmount of the sd-ext to check if the recovery can access the ext) otherwise u can format it from the recovery and then copy back the files from ur pc car reader
Click to expand...
Click to collapse
What is meant to happen when I do a mount/unmount in recovery?
Ano8 said:
What is meant to happen when I do a mount/unmount in recovery?
Click to expand...
Click to collapse
If the recovery can acces the ext, will just say u that is mounted (so everything is ok regarding that partition), otherwise u will get an error like "E:Can't mount dev/block/mmcblk0p2", in this last case u can try formatting the ext from the recovery menu, then restore the files in it (previously backupped) manually
andQlimax said:
If the recovery can acces the ext, will just say u that is mounted (so everything is ok regarding that partition), otherwise u will get an error like "E:Can't mount dev/block/mmcblk0p2", in this last case u can try formatting the ext from the recovery menu, then restore the files in it (previously backupped) manually
Click to expand...
Click to collapse
I went to the recovery menu and then I chose mounts and storage then I chose mount /sd-ext and then nothing happens. I can go and chose unmount /sd-ext, nothing changes except the text that says mount/unmount. No error messages.
What do I do now?
??????????
Bump.......
HELP!
I need to get my Phone working again!
Ano8 said:
HELP!
I need to get my Phone working again!
Click to expand...
Click to collapse
Why u didn't make a nandroid backup? A simple solution now will be to do a fresh install of ur rom again...
Anyway change the thread title.."Boot loop" is too generic, edit it as Boot loop after sdcard repartition URGENT, something like this...(To edit it just edit the first post title)
I hope someone else here can help u..I dont have other ideas, if the sdext is correclty read from the recovery, mean even ur rom should read it and should boot..How much time did u wait? are u sure the boot continue to loop? Go in recovery, wipe cache and dalvik, reboot and wait..U could also do "adb logcat" when ur phone is booting..Search for some guides for it..That will show u some possible errors during the boot that make ur phone bootlooping
Also try this: i read somewhere the ext partition label must be sd-ext (some a2sd script use the label to idenify the partition)(this label is automatically applied when u create/format the ext from the recovery, but as u created the partition ur self from the pc, put that label and see what happen)
andQlimax said:
Why u didn't make a nandroid backup? A simple solution now will be to do a fresh install of ur rom again...
Anyway change the thread title.."Boot loop" is too generic, edit it as Boot loop after sdcard repartition URGENT, something like this...(To edit it just edit the first post title)
I hope someone else here can help u..I dont have other ideas, if the sdext is correclty read from the recovery, mean even ur rom should read it and should boot..How much time did u wait? are u sure the boot continue to loop? Go in recovery, wipe cache and dalvik, reboot and wait..U could also do "adb logcat" when ur phone is booting..Search for some guides for it..That will show u some possible errors during the boot that make ur phone bootlooping
Also try this: i read somewhere the ext partition label must be sd-ext (some a2sd script use the label to idenify the partition)(this label is automatically applied when u create/format the ext from the recovery, but as u created the partition ur self from the pc, put that label and see what happen)
Click to expand...
Click to collapse
I've tried putting the label as sd-ext. Didn't work
I know I have waited long enough because the animation of the skateboarding blue android repeats (he comes in from the side again).
Can you link me a guide of how to do "adb logcat"?
???????????
bump.........
How do I do an "adb logcat"?
Can you show me a guide, please?
I'm using this for Apps2SD
you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Ano8 said:
How do I do an "adb logcat"?
Can you show me a guide, please?
Click to expand...
Click to collapse
ranjii said:
you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Click to expand...
Click to collapse
Ok, I'll do that now...
ranjii said:
you need to install android sdk. after that go to platform-tools folder and run adb.exe logcat
Click to expand...
Click to collapse
I'm getting this error:
/sbin/sh: logcat: not found
HELP!!!!!!!!
Hi all!
I just created an sd-ext partition (ext4) on my sd-card and flashed the INT2EXT4+ script, but it doesn't seem to work.
What I did:
- Go into recovery
- Mount /system
- Installed the INT2EXT4+ script from my sd-card
- Formatted the sd-ext partition
- Rebooted my phone
I've done this a couple of times, but I still have the same amount of internal memory as before I flashed the script. (Before using this script, I tried using Link2SD but that had the same problem..)
And yes, I have init.d enabled and busybox installed and the script is located in the init.d folder.
Does anyone know how to fix this problem?
Btw, I'm using Maclaw's AOSP ICS Final 2.
You may refer to here.
http://forum.xda-developers.com/showthread.php?t=1590807
Try partitioning in CWM. I got S2E to work on CM7 in this way.
cegrade said:
You may refer to here.
http://forum.xda-developers.com/showthread.php?t=1590807
Try partitioning in CWM. I got S2E to work on CM7 in this way.
Click to expand...
Click to collapse
I tried the script/app without repartitioning my SD-card via CWM (I did it via Minitool Partition Wizard, so I didn't have to format my sd-card first) and it still doesn't work.. Should repartitioning via CWM fix the problem?
And btw, in the app description it says "Works on Cyanogenmod........". Since I'm not using Cyanogenmod, this app shouldn't even work, right?
Sorry if I'm being dumb now... :/
Sorry but I don't know if it works on CM rom. Others may know the answer.
I also tried Minitool Partition Wizard but the phone didn't relaize the partition. Then, I tried CWM and it worked.
cegrade said:
Sorry but I don't know if it works on CM rom. Others may know the answer.
I also tried Minitool Partition Wizard but the phone didn't relaize the partition. Then, I tried CWM and it worked.
Click to expand...
Click to collapse
Alright, I'll try that soon then and post the result here!
I don't want to format my sd-card.. :crying:
I have a HTC 816 running lollipop 5.0.2 with cwm recovery it is rooted with su access. I have tried many times to partition my sd with mini partition tool but still get an error stating "mount error invalid argument" I also seem to have a problem installing busybox. I really do need help from a experienced user with much knowledge. I can get more information if needed on request!
Sent from my 710C using XDA Free mobile app
same here, latest CM12 nightly
Have you had anything work for you?
Sent from my 710C using XDA Free mobile app
I currently also have s-on I would like to get it to s-off
Sent from my 710C using XDA Free mobile app
I went to CM12 just to get more space, and it worked, with the same apps I have plenty of space now.
However to get more and more I tried to use link2sd but I had the same error.
Guys, I have written about this around here in some threads. search for it, it won't bite! aside from having the right partition type and right size, you'll have to install the init.d mod too, to allow for Link2SD mount to stick. It totally works so don't get discouraged.
about the other thing, S-Off=Sunshine=25 $. you can find the topic for this too
Is th
Sent from my 710C using XDA Free mobile app
seekfind said:
Guys, I have written about this around here in some threads. search for it, it won't bite! aside from having the right partition type and right size, you'll have to install the init.d mod too, to allow for Link2SD mount to stick. It totally works so don't get discouraged.
about the other thing, S-Off=Sunshine=25 $. you can find the topic for this too
Click to expand...
Click to collapse
Is that the only way to get s-off and what would that do for me
Sent from my 710C using XDA Free mobile app
Has anyone found a way to make links2sd work? I have followed a couple guides but nothing ever works. I have tried ext 2,3,4 and fat32. None ever work to create the mount script.
Andy1058 said:
Has anyone found a way to make links2sd work? I have followed a couple guides but nothing ever works. I have tried ext 2,3,4 and fat32. None ever work to create the mount script.
Click to expand...
Click to collapse
seekfind said:
Guys, I have written about this around here in some threads. search for it, it won't bite! aside from having the right partition type and right size, you'll have to install the init.d mod too, to allow for Link2SD mount to stick. It totally works so don't get discouraged.
about the other thing, S-Off=Sunshine=25 $. you can find the topic for this too
Click to expand...
Click to collapse
Is that the only way to get s-off and what would that do for me
Click to expand...
Click to collapse
Yup, If you don't even know what it can do for you, you probably don't need it you will have freedom to use any regions/ carriers Roms etc IF you know what you're doing and how you're doing it. BUT it also makes Hard Bricking the device that much easier
seekfind said:
Yup, If you don't even know what it can do for you, you probably don't need it you will have freedom to use any regions/ carriers Roms etc IF you know what you're doing and how you're doing it. BUT it also makes Hard Bricking the device that much easier
Click to expand...
Click to collapse
My issue now is link2sd is saying stale NFS file system and I can't find anything about that online
Sent from my 710C using XDA Free mobile app
Andy1058 said:
Has anyone found a way to make links2sd work? I have followed a couple guides but nothing ever works. I have tried ext 2,3,4 and fat32. None ever work to create the mount script.
Click to expand...
Click to collapse
This is what I did for Lollipop (probably will NOT work for Kitkat):
1) Unmount SDcard.
2) Place SDcard in a SDcard reader for a PC.
3) Backup SDcard making a note to look for hidden files.
4) Use MiniTool Partition Wizard to delete all partitions SDcard.
5) Create a primary partition using most of your disk space using fat32 leaving a few GB(I'm using 3GB of 64GB SDcard) for the Link2sd partition.
6) Create a second primary partition with the remaining space using ext2 file system.
7) Restore your files to the primary fat32 partition.
8) Copy the zip file from this thread to the fat32 partition.
9) Return SDcard to phone.
10) Make sure phone mounts SDcard.
11) Boot to recovery and install zip file you copied in step #8.
12) Reboot to system to make sure everything is still working.
13) Run Universal Init.d App. Reboot.
14) Install and run Link2sd from play store.
15) Reboot as necessary. I believe it should only be once... but not sure.
16) Use Link2sd to move apps to second partition on SDcard.
pcjunky said:
This is what I did for Lollipop (probably will NOT work for Kitkat):
1) Unmount SDcard.
2) Place SDcard in a SDcard reader for a PC.
3) Backup SDcard making a note to look for hidden files.
4) Use MiniTool Partition Wizard to delete all partitions SDcard.
5) Create a primary partition using most of your disk space using fat32 leaving a few GB(I'm using 3GB of 64GB SDcard) for the Link2sd partition.
6) Create a second primary partition with the remaining space using ext2 file system.
7) Restore your files to the primary fat32 partition.
8) Copy the zip file from this thread to the fat32 partition.
9) Return SDcard to phone.
10) Make sure phone mounts SDcard.
11) Boot to recovery and install zip file you copied in step #8.
12) Reboot to system to make sure everything is still working.
13) Run Universal Init.d App. Reboot.
14) Install and run Link2sd from play store.
15) Reboot as necessary. I believe it should only be once... but not sure.
16) Use Link2sd to move apps to second partition on SDcard.
Click to expand...
Click to collapse
I will try this tomorrow when I get home hope it works because I just ran out of space!!
Sent from my 710C using XDA Free mobile app
pcjunky said:
This is what I did for Lollipop (probably will NOT work for Kitkat):
1) Unmount SDcard.
2) Place SDcard in a SDcard reader for a PC.
3) Backup SDcard making a note to look for hidden files.
4) Use MiniTool Partition Wizard to delete all partitions SDcard.
5) Create a primary partition using most of your disk space using fat32 leaving a few GB(I'm using 3GB of 64GB SDcard) for the Link2sd partition.
6) Create a second primary partition with the remaining space using ext2 file system.
7) Restore your files to the primary fat32 partition.
8) Copy the zip file from this thread to the fat32 partition.
9) Return SDcard to phone.
10) Make sure phone mounts SDcard.
11) Boot to recovery and install zip file you copied in step #8.
12) Reboot to system to make sure everything is still working.
13) Run Universal Init.d App. Reboot.
14) Install and run Link2sd from play store.
15) Reboot as necessary. I believe it should only be once... but not sure.
16) Use Link2sd to move apps to second partition on SDcard.
Click to expand...
Click to collapse
okay i just got to trying this and i still get the mount script error invalid argument . i believe this is because the script may not be staying in the init.d app on reboot because no new script shows up in it for link2sd unless it doesnt have one but any how its not successful for me.
Benji90 said:
okay i just got to trying this and i still get the mount script error invalid argument . i believe this is because the script may not be staying in the init.d app on reboot because no new script shows up in it for link2sd unless it doesnt have one but any how its not successful for me.
Click to expand...
Click to collapse
How clean is your device? I mean have you installed other mods before trying this one? I had a pretty clean Lollipop system. Just TWRP recovery, supersu and a view apps that use root, but nothing that modified the system(AFAIK).
pcjunky said:
How clean is your device? I mean have you installed other mods before trying this one? I had a pretty clean Lollipop system. Just TWRP recovery, supersu and a view apps that use root, but nothing that modified the system(AFAIK).
Click to expand...
Click to collapse
Its good I have a few other apps and music but still only very basic when it comes to customizations and tweaks. I have tried to install the KitKat version of the tweak previously to see if it works.
Sent from my 710C using XDA Free mobile app
Benji90 said:
Its good I have a few other apps and music but still only very basic when it comes to customizations and tweaks. I have tried to install the KitKat version of the tweak previously to see if it works.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I wonder if the KitKat version is causing the problem? Do you have a clean backup with no patches available?
pcjunky said:
I wonder if the KitKat version is causing the problem? Do you have a clean backup with no patches available?
Click to expand...
Click to collapse
No I don't think so and the KitKat version worked for some people on lollipop too. I don't think they would be interfering because I had this issue before too
Sent from my 710C using XDA Free mobile app
Anyone have any ideas
Sent from my 710C using XDA Free mobile app
Benji90 said:
Anyone have any ideas
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Any progress?
My phone was unstable I think because I removed the wrong system apps with Titanium backup so I started with a clean Lollipop installation and reinstalled all my apps leaving my SDcard unchanged. Everything is fine now. I used Link2sd on most of the non-system apps and now I have 2.29 GB free. I think most of the space comes from getting all most of the Google apps to the SDcard.
A couple of things to check.
1) Verify your second partition is set to primary and ext2.
2) Make sure universal init.d is on by testing it @ the bottom. It should say "Your Kernel Has init.d Support" after you have turned it on.