Help I linked all my games with Link2SD, but the internal storage doesn't move.

Which files are you having trouble with? Link2SD should handle standard stuff like apk, dalvik cache elements fine, even the app's internal data (if you use an ext format partition), but I'm not so sure how well it handles others.

Have you confirmed that the files are downloaded, rather than just the phone not knowing about the links and so mis-reporting the space used? Are you using a file browser which can show you what it a local file and what is a softlink? If not, a terminal emulator and "ls -l <file path>" should show you.

What bits of the app do you move? I know Link2SD has options to move different parts independently. And are you moving stuff to a partition on the card or just forcing the old style move to sd?

To really tell whether it is working you can't trust the system storage menu, as that doesn't know about the partition. So try running Titanium Backup, and at the bottom of the overview screen look for "a2sd storage" and see how much you have and how much is used.

Did you scroll that screen down to make sure there is nothing else below that?

If there is not then the phone hasn't recognised your partition at all (but Link2SD should complain in that case). How did you partition the card? And do you have init.d support in your ROM?

Frankly I recard Minitool as a total piece of crap. Back when I had a HTC Desire (which had so little internal space that most people ended-up partitioning their cards) we had no end of people who had problems with a2sd partitions, and they were always people who'd used Minitool for the partitioning. Even custom recoveries did a better job of partitioning (though they often produced misaligned partitions). GParted would be my recommendation for partitioning cards.

So I'm sorry to say that one thing I'd try now would be to remake the partition (obviously after backing-up the rest of the card).

Also, are you using a stock ROM or custom? The reason is that most custom ROMs will support init.d scripting, while stock ROMs usually don't without modification. This is important as I'm pretty use Link2SD relies on an init script to manage mounting of the partition on boot, so if you use that without init support it could explain it failing (especially if it failed after rebooting the phone). Please note that I've not used Link2SD for several years, so I'm relying on memory for this, but this is worth checking before repartitioning the card.

Then you have the stock ROM. "Stock" just means "what it comes with".

This means that you probably don't have init.d support. I'm pretty sure that Link2SD will have added an init script (look in /system/etc/init.d for something called 10apps2sd, or something similar). If the phone doesn't actually run that on boot then it's likely to break your Link2SD's app moving at some point. It's possible that your play store error 24 is related to that, especially if these are apps that you are trying to update rather than things you've never installed before: that error typically happens when there are app data left behind from an app that is not installed, so if you've moved apps and then the links are broken that could well produce this effect.

There are some XDA threads about enabling init.d support in stock ROMs. This one still has an active discussion (I've only glanced at the first post, and as I don't know what device you have I obviously cannot guarantee compatibility, but it would seem worth a go). Another solution is here, which I think should work too.

If your "just rooting" included installing a custom recovery, then do take a backup using it before messing with the system in any way (I'd personally include "before installing Link2SD" in that). If it doesn't, finding a custom recovery for your phone is something I'd recommend. I have a low opinion of rooting methods which just root the ROM without installing a custom recovery, because they give you more ways to mess up without providing the tools to back up and easily fix problems. Of course not all phones have custom recoveries built for them, in which case there's not much more you can do - you really must not install a recovery that was built for a different phone!

If enabling init.d is all that is needed then it might be that just doing that and rebooting will fix it without any need to remake the links. That would be the simplest solution. If you just have a rooted stock ROM it's very unlikely you currently have init.d support.

If that isn't enough to fix it, and you need to remake the partition, then the problem is that the data that are already on the partition will be lost. Ideally you'd move it all back to the phone first, but that's not an option (if you could do that then it would be working anyway). You can of course wipe the links with a root-capable file browser (X-plore, Root Explorer, even ES File Manager), if you know where to find them all: some will be in /data/app, some in /data/data. I can't absolutely guarantee there aren't any others, but if you can find a 10app2sd script in /system/etc/init.d then that will show you where it has placed links (open it with a text editor or even a browser). But if you have parts of the app or its data still in internal storage you may have problems reinstalling (e.g. the error 24 problem you are seeing). So it may be that a factory reset is needed. That's why I'm hoping that enabling init.d will be enough.

Interesting: the last time that I used Link2SD it used the /system/etc/init.d folder to store a startup script, and I'm surprised if it has changed something so basic. Of course if you didn't have an init.d folder I don't know whether it would have created one, but I was kinda hoping it would, because if not I don't know what else it might have done (I would have hoped it would have produced an error message if it couldn't do an important bit of the setup).

Farcrydud said:

How do I enable init.d

Click to expand...

I posted links to two methods of doing this in post #14 of this thread.

If your phone is rooted you should have either SuperUser or SuperSU - there's no way you could have used root privileges otherwise. Both do the same job, so I would expect either to be fine.