Does anyone know how to update the mount points so that when I insert a microsd card it is mounted to the mnt/sdcard folder? I still would like to be able to use the internal storage though. Maybe it can be mounted someplace else.
I ask because I would like to backup my apps to the SD card using Titanium backup and Astro. Backing up my apps to the internal memory makes no sense. Especially when you are trying to move Angry Bird saved games between devices.
I did the opposite when I was running the CM7 on the GTablet: all the ROMs mapped sdcard to the internal memory while CM7 had it the way you want it. I didn't need an SD card for the GTab, so suffice to say, I updated it to change it back so all my apps would work again.
Anyway, you need root, and all you have to do is find /etc/fstab and change the mount points to where ever you want them. On the GTab, I just switched emmc and sdcard around. This worked on Android 2.3, so I assume its the same for 3.x. I don't have my Transformer with me here at work or I'd look to make sure.
IMPORTANT: Make sure you make a system backup before you mess with it, cause you could mess up the file and then nothing will mount on start up, so proceed at your own risk.
http://forum.xda-developers.com/showthread.php?t=1122710
Last page has a script you can use or you can use the app method, I think it is towards the end of the 2nd page, its a 1.99 app but works fine and survives reboots
EDIT: Post 38 and 41
I've been searching both this forum and the net generally and not found an answer to my specific problem so I'm hoping someone can help.
I'm trying to swap out my ROM, I'm currently running CM 11 nightly but I'm getting endless FCs with apps so thought I'd try something different.
When I try to run the nandroid backup with TWRP v2.7.0.1 the backup fails every time with the error E: unable to mount '/sd-ext'
Can anyone advise? Thanks
tht looks like external sd card.
Try changing location for your backup to internal memory or make sure you got SD card plugged in to SD slot.
you may also try command on terminal emulator (or via adb shell):
ln -s /storage/emulated/0/ /sd-ext/
it will create symbolic link named sd-ext in root of your system and it will point to internal storage (if I am not mistaken, from now on it should not matter if you select internal or external storage as target for your backup - it will end up as internal anyways)
Sent from my TF300T using XDA Free mobile app
Thanks, the backup was to be created on the internal SD card, but you are right it is almost certainly a problem with the external card. I'm unable to mount either the dock SD or micro SD cards in TWRP - the options are just greyed out and can't be selected.
I can't get either card to mount when I boot to system ether I have noticed. I've tried formatting them as FAT32, EXFAT and NTFS and no dice so I'm wondering if this is a KK issue - they both worked flawlessly when I was running PA and Omnirom JB ROMs.
I've managed to find a workaround - I've flashed CWM and have been able to do a nandroid backup with that - but I still can't mount either the micro SD or dock SD cards with CWM or in system when I flashed KatKISS ROM - and of course now I can't use any old TWRP nandroids I have from JB ROMs without reflashing TWRP. I'd also rather be running TWRP ultimately if I can so it would be good to get to the bottom of what is causing this issue.
Not quite sure what the command line you suggested does, but I'm guessing it won't be useful with the problem as it stands now?
sorry for late reply as I was out of internet lately.
that command creates /sd-ext/ folder that acts similar to shortcut to intertnal sdcard
any call for /sd-ext (for example: cd /sd-ext) will end up on internal sdcard.
That wont help with accessing your external sdcard (as this was main issue here) - it would merely fool installer to 'think' it is working on external sd while it was still on internal.
Sent from my TF300T using XDA Free mobile app
Thanks for your help. I've had endless troubles which ultimately ended in a hard brick during a failed flash of the stock ROM. I'm waiting for a replacement motherboard - something wasn't right with the old board anyway, it doesn't seem that it was just ROM issue. Hopefully when it comes I'll find that it wasn't a hardware issue associated with the SD cards as well.
While working with Link2sd, I moved a ton of apps to the SD's 2nd partition, using f2fs file system. Rebooting the phone (XT926 - 4.4.2 - rooted), the 2nd partition was no longer accessable and, of course, the apps vanished. Worse, I can't re-install some of them. I get the "not enough storage" gripe. Short of doing an FDR, is there any hope of recovering the data or at least making it possible to re-install the lost apps? FWIW, I tried reading the SD under Win7 (nothing found, of course) and SuSE Linux with f2fs.tools installed. Still nothing.
How SOL am I?
I did an FDR.
It looks as though EXT3 is a workable choice. Right? Wrong?
I posted following is posted at the end of Working CWM Recovery for LOCKED 183.46.15 + Deodex and more
[... I]t appears that two related problems have shown up. And those error messages lead to 2 points.
A) Apps like Link2SD and Apps2SD, which move data from the internal "SD" to a real SD, fail to work. The errors all feature some form of the mount failing.
B) busybox isn't visible to these apps.
Busybox is located in /system/xbin. The link apps try to mount a second partition on the external SD. The mount utility is supplied by busybox. The errors say that /sbin/busybox can't be found. I think the system PATH is supposed to make calls to /sbin/busybox resolve to /system/xbin/busybox. I created a symlink from /system/xbin/busybox to /sbin/busybox. That changed the nature of the error messages somewhat but otherwise didn't correct the "mounts don't work" problem. After rebooting the phone, the symlink had to be created again as it wasn't present after the reboot.
I spent a lot of time with the Apps2SD developer (no reply from the Link2SD developer), trying to figure out what was going wrong. At the end of the day (literally), the problem was, in her mind, the ROM. Of course the ROM in the MAXX HD is locked up, so that can't be the source of the problem. But... is it possible that deodexing, or at least the process that installed the deodexing mod, subtly broke something related to busybox?
Click to expand...
Click to collapse
There isn't much to be added here except to ask if anyone has used one of the "link to SD" apps successfully.
RBEmerson said:
While working with Link2sd, I moved a ton of apps to the SD's 2nd partition, using f2fs file system. Rebooting the phone (XT926 - 4.4.2 - rooted), the 2nd partition was no longer accessable and, of course, the apps vanished. Worse, I can't re-install some of them. I get the "not enough storage" gripe. Short of doing an FDR, is there any hope of recovering the data or at least making it possible to re-install the lost apps? FWIW, I tried reading the SD under Win7 (nothing found, of course) and SuSE Linux with f2fs.tools installed. Still nothing.
How SOL am I?
Click to expand...
Click to collapse
Sent from my Eon_62i using XDA Free mobile app
You don't say... [/wink]
So does Link2SD not work with f2fs? I get "Second partition not found"
OK guys, I had a problem recently with games not being able to find their obb expansion files after linking/binding them to SD card 2nd partition with Link2SD. I could link anything else, like the game's internal data, library files, etc, and they would still work. But after linking the obb file, they stopped working. I remember this working fine on previous phones I've owned, so I figured that this must be an issue with how the stock system deals with interacting with the SD card, creating symbolic links, etc. Or more specifically a faulty 'sdcard' file at /system/bin/sdcard. I never had any issues with this when running unofficial CM12.1 on the v10 as far as games not working when their obbs were linked (except CM kept crashing so I switched back to stock). So I figured that maybe replacing the sdcard file with the one from CM might work. And my hunch was right.
I bought a 200GB SD primarily so I could link games and other big apps, this failure really pissed me off. Especially having spent a decent amount on it and not being able to use it for what I bought it for!
This fix may also work for games not working after binding their obbs with FolderMount, or with the Xposed module Obb On SD (http://repo.xposed.info/module/com.smartmadsoft.xposed.obbonsd). I havent did extensive testing with these, so if anyone wants to try and report back, then feel free.
Why should you trust me? Well, you don't have to. Go ahead and link a game obb with Link2SD, while using the standard sdcard file. Then launch the game. It most likely wont work, will probably say that it couldn't find its' data, need to download files and fail, etc. Then flash the zip I'm providing and try again. Your linked games should now work. Be sure you back up the original sdcard file in case you run into issues. I havent found any yet. Your SD should still be available on boot, and if you have an EXT4-formatted SD in conjunction with the Evil Yummy Gumdrop kernel, it will be available as well. I've only tested with the T-Mobile variant of the v10, but this should work with other variants, as long as you have root access, mount /system as writable, and replace the file. Permissions should be set to 0755. If you don't have a custom recovery then you can also try flashing with FlashFire (http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 and https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en)
The only caveat I've run into is that X-plore, my favorite file manager, now both shows a "Internal storage" and "/storage/emulated" heading, which both link to the same area (internal/emulated storage). No big deal.
I hope this fix helps some people out. Report back and give thanks.
Edit: I havent tried this with Marshmallow, I doubt it would work, because of how MM handles external SDs. Try at your own risk. This has only been tested on a stock rooted Lollipop 5.1.1 ROM on the T-Mobile LG v10.
Edit#2: I just finished testing this with FolderMount and Obb On SD. They work flawlessly, but didnt before. No major issues yet.
I'm using Marshmallow now, so I cant provide any support for this. This file doesnt work on MM, I'm trying to find a new fix.
Can you provide a solution for marshmallow? I'm facing the problema only on marshmallow
Can I ask you a question. I purchased this phone because is 64GB and that's just about perfect for my green plus games. And I play RPGs which are GB heavy. So why l Iink2sd?
Any news?
I found 2 solutions which work on MM and Lollipop, and they don't involve replacing system files. One is an app, the other needs Xposed. I no longer recommend using Link2SD with MM, since it seems to be incompatible anyway. Some people did manage to get it working, but still no obb linking. Here are 2 superior solutions:
1. XInternalSD:
Download via Xposed Installer, activate module, reboot. Open a root file manager, go to /storage/, look for the folder that goes to your external SD's 1st partition. Open XInternalSD, where it says 'path to internal SD card', make sure it contains the right path to your external. The point is to trick certain apps (mostly games) into thinking your external is the internal storage. Check the box that says "full access to external SD". You can either "enable for all apps", or just certain apps. I recommend only for apps where obb linking doesn't work. Go to /storage/<external path here>, go into Android folder, create obb folder if it doesn't exist. Next, install your games. If you get them from Play Store, you will need to manually move the obbs to the folder above *before* running the app. Make sure you move the obb file itself *and* the folder above it. As an example, the game "Secret of Mana", my path looks like /storage/<external>/Android/obb/com.square_enix.secret/main.201410302.com.square_enix.secret.obb. When you have finished moving, open XInternalSD, tap "enable for apps", put check beside your app, then OK. Then you can run the app, this method should work for most regular apps and games. The downside of this approach is that you can only force an app to store most/all of its' external data on SD. External data is defined as anything that is stored on internal or external storage. All other parts of an app usually go into /data.
2. Apps2SD (search in Play Store):
There are free and paid versions (2nd is called Apps2SD Pro). I think free version has same features as Pro, but with ads. You can deal with them, block ads with the hosts file, or use Lucky Patcher to patch out the ads/create a modded APK with no ads. I recommend you buy pro version, it has so many features, and is way better than Link2SD, and is MM/Nougat-compatible. It's updated often and only costs a few dollars at most. *Please* don't steal from this great developer.
Anyway, for this to work, your SD needs 2 partitions. Apps2SD has a partitioning tool, I tried it, it deleted all my files. You can still use the app's partition tool to create 2 partitions, then copy your personal files back when finished. 1st partition is for personal stuff, 2nd partition is for Link2SD/App2SD (I dont recommend storing other files here, but App2SD shouldnt mess with them). I assume most people use Windows, so backup all your SD files to PC, online, wherever, just in case. Download the free version of MiniTool Partition Wizard, resize the first partition so that it's smaller. 1st partition should either be exFAT or FAT32. Then create 2nd partition, format it as ext4. You can use almost any Linux-based filesystem for 2nd partition, but I recommend ext4. Choose whatever size you want for each. You can also use any other partitioning tool of your choice (I prefer GParted, a Linux software). Then put SD back into phone and install App2SD. Make sure you use v11.4 of the app or newer, this is the version that fixed sdcardfs, which is what causes this problem in the first place, and why I started this topic. Tap "link apps to SD card", select ext4 (if this is what you used) and advanced mount option. I have tried the init.d and su.d methods, but after rebooting I got errors like "root access denied", "soft reboot required", and linked apps missing. Advanced method has something to do with Android's vold, is all I know, but works flawlessly for the v10 MM. Apps2SD is better than XInternalSD because you can link all parts of an app (APK, dex/odex, libraries, internal/external data, and caches), XInternalSD only works for external data and obb files.
For Apps2SD, you also need this file:
https://forum.xda-developers.com/attachment.php?attachmentid=3987630&d=1483343643
Unzip the file, force stop Apps2SD, then go to /data/data/in.co.pricealert.apps2sd.pro/app_binary/apps2sd. Delete this file, leave the rest. Then copy the file from the zip into the same folder. For the next part you need to set permissions, I use Total Commander. In TC I hold my finger on the file, select Properties, select RWX, type 777, then Apply. Go to Properties again, select UID, in both fields select the # that says Apps2SD, then Apply again. You can use any root file manager for this, instructions will vary, I just used TC as an example (great and powerful app, BTW). Make sure you do this step. This fix may not be needed in future Apps2SD version, so my advice is dont do this unless obb/external data linking doesnt work or gives an error ("invalid argument"). But this is definitely necessary for v11.4.
If you are still having issues, try these:
In SuperSU, disable mount namespace separation and enable su on boot.
Try setting SELinux to permissive instead of enforcing. For this you can use SELinux Mode Changer, an init.d/su.d script, or you can manually type "su" then "setenforce 0" in a terminal app.
Change your root management app. I used to use SuperSU, but switched to phh's Superuser not too long ago. There is a regular version and a Magisk version, take your pick. I'm loving it and have no intention of going back to SuperSU unless I have serious issues (none so far in the few months I've used it).
XInternalSD only requires Xposed but doesnt need root access, so it may be better for unrooted users. The Xposed framework itself can be installed into system partition with no need for being rooted, but I do believe that the systemless version of Xposed needs SuperSU. The one exception I can think of is the Magisk version of Xposed, which only needs Magisk but not root.
Apps2SD needs root, except maybe for the regular/normal mounting method (haven't tested that). I'm not aware of any solutions for unrooted users, your choices are very limited.
In further testing FolderMount and Obb On SD still do not work with v10 MM. I also dont recommend using adoptable storage for your SD, it's confusing and too much of a headache.
As of v11.5 of Apps2SD Pro, the part about manually replacing the appp2sd binary file is no longer necessary. You only need to do this if you're using v11.4.
Apps2SD v11.5 also supports systemless modification/injection, so that the app can do its' work without modifying the /system partition. But you need SuperSU installed, modifications are installed to /su.
I no longer own the v10, I got sick and tired of the issues I was having with it. I found a good deal on EBay for a new Note 4 still in the factory-sealed box. It does not exhibit any of the linking/obb binding issues I was having. So I can't provide support for this anymore. The last time I had the v10 was a few weeks ago, running stock modded Marshmallow. At that point Apps2SD Pro worked perfectly on it for all my needs, it solves all linking/binding issues without replacing system files, and only needs root. It's only a few $$$ and the dev updates it often. It also has support for SuperSU, Magisk, phh's Superuser, and pretty much any other root solution out there. So that's my final word, this app is your best bet.
Can I do something to undo this, it made both my internal and external storage disappear.
@NguyenDucAnh01: If You made a copy of the original sdcard and vold files, then you can just restore them to /system/bin/. Set permissions to 0777, you can do this from TWRP. If you didn't make a backup then you will have to reflash your firmware.
Thanks man
AnonVendetta said:
@NguyenDucAnh01: If You made a copy of the original sdcard and vold files, then you can just restore them to /system/bin/. Set permissions to 0777, you can do this from TWRP. If you didn't make a backup then you will have to reflash your firmware.
Click to expand...
Click to collapse
Thanks for the suggestion, but I found a way myself :highfive:
Since the script only replace sdcard file, I take the one from the original rom, replace the file in that .zip with it, then adb sideload it with TWRP
Also that srcipt didn't backup the file, I had to do that way.
@NguyenDucAnh01: I now recommend using Apps2SD instead of Link2SD, it has many more features and is more up to date. You can get it for free in Play Store. With this app it isn't necessary to replace system files at all. And it works on all Android versions up to Oreo, haven't tested with Pie yet.
XInternalSD, Obb On SD, and FolderMount should work too, in most cases. But the first 2 need Xposed.
Oh, one more thing, I no longer own the LG v10, not for a very long time. I'm now using a ZTE Axon 7. The v10 is the worst phone I've ever owned.
Hello.
As a new member i can't post messages in Custom Firmware topic,so i've been sended here
Here is the problem.
I have installed SuperMan 2.0 Custom ROM,with Super Stock kernel with SuperSu root,Android 7.
And somehow i cannot transfer games (OBB files for example) to SD card.I tried to use App2sd,i formatted sd by using instructions into two sections Fat32 and Ext4.Program should transfer games(or other apps)to second section of card(to ext4),and this section is succesfully is mount and also mount OBB files like no problem,but games no working! App2sd don't gave me any errors,consider app info it's should be work fine,tried different games no same resultŠ±no working after transfer OBB to EXT4 section of sd card by using app2sd.
Then after some failed tries,just decided to go back to usual FolderMount.
After installaton i mount games OBB derictories as usual(not first time using this app),app didn't gave me any errors too.
But when i tried to launch any games....no one works.
The only system app i installed is a Lucky Patcher,and titanium Backup,that's all.
So i have a feeling that something wrong in the ROM,something blocking to emulate sd as internal memory for files,coz Foldermount always did worked before without problems.Or maybe it's Android 7 some issues?
Maybe someone could have any idea how to solve this wierd problem?
Thanks.