Related
Unlike every other rom I've tried Cyanogen doesnt automatically mount the externalsd folder and its located in /mnt/emmc
Now I know I can run the bind command to get the folder to go to its original location, by running mount -o bind /mnt/emmc/ /mnt/sdcard/external_sd
but that just disappears after the phone is rebooted, I would like to know how to run the command automatically at startup maybe via a script (which I have no idea how to write)
Its a minor annoyance in samsung cyangoen but I'm hoping it can be easily fixed, any help appreciated.
Thanks
Alright so here's the deal, my internal SDCARD is corrupted and the /data partition is unusable.
My device is i9003 and it's running on MIUI at the moment. By default MIUI didn't detect my external SD or my internal SD but after editing "vold.fstab" I was able to mount the first partition of my external SDCARD as external memory and everything was good, I could finally use the camera and pretty much do everything else.
But I was still unable to mount the second partition of my external SDCARD as my internal memory which meant none of my messages could be saved and the phone would pretty much go back to factory settings after a reboot, this apparently is because the /data partition (present on the internal memory) stores all the user data such as the time, the theme I'm using, etc and not having a /data partition meant none of these settings were really saved.
Having no internal memory also means I cannot install any apps such as Link2SD.
Moving on, after many hours of googling I found out that it might not be possible to mount the internal memory using "vold.fstab" and the only way to do it could be by mounting the memory manually during init.
So here's what I want again, I want to use the second partition of my external SDCARD as internal memory, this is likely to solve all my problems and make my phone usable again.
Thanks for all the help, appreciate it.
You need to edit /init.rc (or init.vendor.rc). To make the edits here stay, you'll need to create a new boot.img to flash your device with.
Have a look at an extract of mine init.<vendor>.rc:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
#mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
# Use below two lines instead of above to run /system from SDcard instead of internal flash
mount ext3 /dev/block/mmcblk0p3 /system
mount ext3 /dev/block/mmcblk0p3 /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
Compare the lines I've commented out with the others. Here both /data and /system resides on the SDcard, you only need to care about /data. Also remember your device nodes may not be named "mmcblk0p3" etc.
But you'll need to make those changes in the initramfs in your flashed boot.img to make them stay.
kuisma said:
You need to edit /init.rc (or init.vendor.rc). To make the edits here stay, you'll need to create a new boot.img to flash your device with.
Have a look at an extract of mine init.<vendor>.rc:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
#mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
# Use below two lines instead of above to run /system from SDcard instead of internal flash
mount ext3 /dev/block/mmcblk0p3 /system
mount ext3 /dev/block/mmcblk0p3 /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
Compare the lines I've commented out with the others. Here both /data and /system resides on the SDcard, you only need to care about /data. Also remember your device nodes may not be named "mmcblk0p3" etc.
But you'll need to make those changes in the initramfs in your flashed boot.img to make them stay.
Click to expand...
Click to collapse
Thanks for the reply man, mind telling me the how I can go about doing this?, I've got the ROM I flashed via CWM here with me, I could send it over to you if that would make things easier for you.
EDIT: would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img? In case it's the latter, I'm going to need help doing it.
PhantomPhreek said:
Thanks for the reply man, mind telling me the how I can go about doing this?, I've got the ROM I flashed via CWM here with me, I could send it over to you if that would make things easier for you.
Click to expand...
Click to collapse
You'll find a good tutorial about how to work with boot images here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
If you already got the ROM in a file, this should be easy! Got ADB and FASTBOOT as well?
kuisma said:
You'll find a good tutorial about how to work with boot images here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
If you already got the ROM in a file, this should be easy! Got ADB and FASTBOOT as well?
Click to expand...
Click to collapse
I'm not sure I've got FASTBOOT but I've definitely got ADB and I've also got the ROM. Would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img?.
PhantomPhreek said:
I'm not sure I've got FASTBOOT but I've definitely got ADB and I've also got the ROM. Would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img?.
Click to expand...
Click to collapse
No. You need to reboot the phone for the init.rc script to execute, and once you reboot the phone, the root file system is overwritten by the flashed image ... Catch 22.
You'll NEED to create a new boot.img with a new initramfs containing your changes.
kuisma said:
No. You need to reboot the phone for the init.rc script to execute, and once you reboot the phone, the root file system is overwritten by the flashed image ... Catch 22.
You'll NEED to create a new boot.img with a new initramfs containing your changes.
Click to expand...
Click to collapse
Shucks, this explains why it didn't work. Alright, so I extract boot.img from the rom, follow the tutorial.What is it that I have to edit again? "/init.rc" or "init.<vendor>.rc"?.
Thanks for the help man, appreciate it.
EDIT: Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?
PhantomPhreek said:
Shucks, this explains why it didn't work. Alright, so I extract boot.img from the rom, follow the tutorial.What is it that I have to edit again? "/init.rc" or "init.<vendor>.rc"?.
Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
Of course, MIUI may have some boot hooks you could use to re-mount /data after boot. I know nothing about that ROM. Also keep in mind that each time you update the ROM, you have to remake this edit.
Also, no idea what MIUI calls its init.rc, you'll just have to see for yourself. If you've got the mount commands in init.rc, fine. Else look elsewhere.
A good first step would to make sure you really are able to flash a new boot.img. Download fastboot and verify your device understands it. Else you have to use some proprietary flash program, and I'm not familiar with Samsungs bootloaders at all. Ask in the Samsung forum if so.
kuisma said:
Of course, MIUI may have some boot hooks you could use to re-mount /data after boot. I know nothing about that ROM. Also keep in mind that each time you update the ROM, you have to remake this edit.
Also, no idea what MIUI calls its init.rc, you'll just have to see for yourself. If you've got the mount commands in init.rc, fine. Else look elsewhere.
A good first step would to make sure you really are able to flash a new boot.img. Download fastboot and verify your device understands it. Else you have to use some proprietary flash program, and I'm not familiar with Samsungs bootloaders at all. Ask in the Samsung forum if so.
Click to expand...
Click to collapse
Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?. ADB and I do see the file init.rc and I also see the mount commands as well. I used adb shell to run the command you sent over with a few edits for second partition and it does mount but as you said, it all goes away after reboot.
PhantomPhreek said:
Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?. ADB and I do see the file init.rc and I also see the mount commands as well. I used adb shell to run the command you sent over with a few edits for second partition and it does mount but as you said, it all goes away after reboot.
Click to expand...
Click to collapse
Hmm... are you even able to create a second ext3 partition on the SDcard using Windos..?
kuisma said:
Hmm... are you even able to create a second ext3 partition on the SDcard using Windos..?
Click to expand...
Click to collapse
haha, I used CWM to create the partitions initially, but then I used a software called MiniTool, works well. Can I get you to to do it?
PhantomPhreek said:
Alright so here's the deal, my internal SDCARD is corrupted and the /data partition is unusable.
Click to expand...
Click to collapse
The ROM you are using requires an ext4 partition as partition #3 of the SDcard. This is mounted as /data. Repartition your SDcard #1 as FAT, #2 whatever, and #3 as ext4, and everything will work as intended. :victory:
I guess you've missed this in the ROM documentation ...
kuisma said:
The ROM you are using requires an ext4 partition as partition #3 of the SDcard. This is mounted as /data. Repartition your SDcard #1 as FAT, #2 whatever, and #3 as ext4, and everything will work as intended. :victory:
I guess you've missed this in the ROM documentation ...
Click to expand...
Click to collapse
Wah~ really?, I'll try that and get back here with the results. Thanks a lot!.
EDIT: Is it FAT or FAT32?
PhantomPhreek said:
Wah~ really?, I'll try that and get back here with the results. Thanks a lot!.
EDIT: Is it FAT or FAT32?
Click to expand...
Click to collapse
FAT32.
kuisma said:
FAT32.
Click to expand...
Click to collapse
Tried but didn't work out. I made three partitions, all primary - #1 FAT32, #2 FAT32, #3 EXT4. Plugged the SDCARD in and the external memory was detected as usual, but not the internal memory.
I tried changing the time, it was reset back after reboot.
After that I left the SDCARD as is and flashed the ROM again and now, neither the internal nor the external memory are detected. This is probably because the "vold.fstab" which was edited by me, was overwritten on re flashing.
I'm at a dead end, any ideas?
PhantomPhreek said:
Tried but didn't work out. I made three partitions, all primary - #1 FAT32, #2 FAT32, #3 EXT4. Plugged the SDCARD in and the external memory was detected as usual, but not the internal memory.
I tried changing the time, it was reset back after reboot.
After that I left the SDCARD as is and flashed the ROM again and now, neither the internal nor the external memory are detected. This is probably because the "vold.fstab" which was edited by me, was overwritten on re flashing.
I'm at a dead end, any ideas?
Click to expand...
Click to collapse
Attach an output of "df", "mount", the file "/init.latona.rc" and "/etc/vold.fstab" here, and I'll have a look at it. Hmm... include the output of "dmesg" as well, to be on the safe side.
kuisma said:
Attach an output of "df", "mount", the file "/init.latona.rc" and "/etc/vold.fstab" here, and I'll have a look at it. Hmm... include the output of "dmesg" as well, to be on the safe side.
Click to expand...
Click to collapse
What bugs me is the fact that the external SD is not detected, from what little knowledge I have, external SD is unrelated to the internal SD which I currently have problems with, meaning it should be detected without a problem.
Also I have to add, CWM doesn't detect my external SD right away, when I go to recovery and go over to "Choose zip from sdcard" it says "E:Can't mount /sdcard/". The solution I've found coincidentally is to go to "mounts & storage", mount "/emmc", pull the SDCARD out plug it in again and then "mount /sdcard" this works perfectly and I'm able to flash roms from the sdcard.
One problem at a time, please. Attach the files I requsted, so we can determine why /data failes to mount. Looking at your ROM:
Code:
$ grep " /data$" init.latona.rc
mount ext4 /dev/block/mmcblk0p3 /data
I want to know why this fails, and I guess the answer is in the dmesg output. And please before I'll get another whiskey.
kuisma said:
One problem at a time, please. Attach the files I requsted, so we can determine why /data failes to mount. Looking at your ROM:
Code:
$ grep " /data$" init.latona.rc
mount ext4 /dev/block/mmcblk0p3 /data
I want to know why this fails, and I guess the answer is in the dmesg output. And please before I'll get another whiskey.
Click to expand...
Click to collapse
I can't seem to find "/init.latona.rc" everything else you requested I've mailed them over already
EDIT: the dmesg output is AFTER I mounted "/sdcard" manually as explained in my previous post.
PhantomPhreek said:
I can't seem to find "/init.latona.rc" everything else you requested I've mailed them over already
EDIT: the dmesg output is AFTER I mounted "/sdcard" manually as explained in my previous post.
Click to expand...
Click to collapse
The files you mailed me does not correspond to the ROM you refereed.
The /etc/fstab show that /data is mounted as an rfs file system, not ext4. So either format partition #3 on the sdcard as rfs (Samsung proprietary), or edit /etc/fstab and change "rfs" to "ext4". I'd prefer the later, assuming your kernel supports ext4. Else use ext3.
Code:
/dev/block/mmcblk0p3 /data rfs rw
But you can't have flashed the ROM you told me you did. It excepted an ext4 file system ...
I jumped from stock to CM10 and have found an issue I need resolved, but am not sure how to go about it.
On stock, I didn't have
/sdcard/ is the path for the internal memory
/sdcard/external_sd/ is the path for the actual add-in slot you buy yourself.
This is great because the file explorer apps don't need special access to get to, and things are at least somewhat logical on how they're laid out.
On CM10:
/storage/sdcard0/ is internal memory
/storage/sdcard1/ is external memory
There are symbolic links of /sdcard and /external_sd but to access the latter, I need to tell apps like ES file explorer to change their base path rather than just having a nested mount structure.
I've tried using terminal emulator to go in and create a symbolic link, but I get 'operation not permitted' messages. I've also tried editing /etc/vold.fstab to have it change the mount from /storage/sdcard1 to /storage/sdcard0/external_sd, but the filesystem is read-only and 'mount -o remount,rw /' doesn't have an effect even though it doesn't complain.
How can I change the mount structure back to how I want it and how it's easier to access/navigate it in my apps?
Run into some situation, hopefully someone can shed some light
Did you mount this files as r/w?
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Did you mount this files as r/w?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
In my original post I mention trying to get it remounted as r/w, the command doesn't complain but the filesystem stays read-only.
Try busybox mount -o remount,rw /system
If that fails, use an app to do it.
ChronoReverse said:
Try busybox mount -o remount,rw /system
If that fails, use an app to do it.
Click to expand...
Click to collapse
Any particular apps to recommend? I had tried issuing the remount command on / and not /system. I will give that another try.
ChronoReverse said:
Try busybox mount -o remount,rw /system
If that fails, use an app to do it.
Click to expand...
Click to collapse
I was able to modify the mount point to be /storage/sdcard0/external_sd/ for the external SD slot, but when I rebooted CM it got stuck and would buzz every 10 seconds or so and stayed that way indefinitely. Not sure why this breaks CM so bad but there you have it. Oh well.
Might be a better idea to just add links so you get your old /sdcard/external_sd
I'm not currently on a CM10 ROM or else I'd test.
ChronoReverse said:
Might be a better idea to just add links so you get your old /sdcard/external_sd
I'm not currently on a CM10 ROM or else I'd test.
Click to expand...
Click to collapse
Symbolic links don't work on a FAT based filesystem (which the SD card mounts are), unfortunately.
My situation: Galaxy S3 with latest (26 Oct. 2012) update to 4.1.1 via Kies. Then rooted. Works smoothly. External Sd-card visible, no problem.
Then:
repartitioned SD-card with gparted in Fedora machine: mmcblk1p1 with old contents, mmcblk1p2 for new contents, both vfat. Filled mmcblk1p2 with contents from linux machine.
In the phone the first partition (the one with the old data) is recognised as before. The second partition is not seen.
By using the terminal emulator as super user I can mount the second partition by the command:
mount -rw -t vfat /dev/block/mmcblk1p2 <mountpoint>
<mountpoint> is a directory VISIBLE to File Explorer.
After mounting, however, the directory contents are NOT visible in File explorer (even after stopping and restarting File explorer) but can be listed perfectly in the terminal emulator. Giving the cp-command for copying of an individual (MP3) file from the <mountpoint> to the folder Music shows the copied file in that folder and the music can be played in the usual way through the GUI.
Question:
Does anybody have an idea how to make the mounted 2nd partition visible to the apps so that the files can be accessed though the GUI?
Thanks for thinking about this problem.
Bananiel-1944
Found the solution by some more thinking after all:
mount -rw -t vfat -o umask=0000 /dev/block/mmcblk1p2 <mountpoint>
The -o umask=0000 is essential, otherwise the permissions are rwx------; with the umask option they are rwxrwxrwx and thus can be reached.
For safety sake, mount when needed and umount promptly afterwards.
Bananiel-1944
Bananiel-1944 said:
My situation: Galaxy S3 with latest (26 Oct. 2012) update to 4.1.1 via Kies. Then rooted. Works smoothly. External Sd-card visible, no problem.
Then:
repartitioned SD-card with gparted in Fedora machine: mmcblk1p1 with old contents, mmcblk1p2 for new contents, both vfat. Filled mmcblk1p2 with contents from linux machine.
In the phone the first partition (the one with the old data) is recognised as before. The second partition is not seen.
By using the terminal emulator as super user I can mount the second partition by the command:
mount -rw -t vfat /dev/block/mmcblk1p2 <mountpoint>
<mountpoint> is a directory VISIBLE to File Explorer.
After mounting, however, the directory contents are NOT visible in File explorer (even after stopping and restarting File explorer) but can be listed perfectly in the terminal emulator. Giving the cp-command for copying of an individual (MP3) file from the <mountpoint> to the folder Music shows the copied file in that folder and the music can be played in the usual way through the GUI.
Question:
Does anybody have an idea how to make the mounted 2nd partition visible to the apps so that the files can be accessed though the GUI?
Thanks for thinking about this problem.
Bananiel-1944
Click to expand...
Click to collapse
Dear Bananiel,
your post was closest to the solution of my problem, maybe you could suggest something that will finally help me.
I've partitioned external SDcard with CWM to be used for Link2SD. Link2SD's script works fine and the EXT2 partition mounts well. The problem is with the FAT32 partition which can't be mounted by android (I get "SD card empty of file system damaged" in the notification area). When I go in CWM recovery mode I can mount that partition by choosing "mount USB storage" option and then I can see it on my PC. Partition is healthy and PC has no problems with it.
I've tried issuing commands you've suggested in your post through ADB SHELL, after that when I go to folder that I've designated as mount point I can see files from non-working partitio, but the message in notification area still persist. Also the change is not permanent, after reboot I have to do that again.
Thanks in advance for any help given.
Bananiel-1944 said:
Found the solution by some more thinking after all:
mount -rw -t vfat -o umask=0000 /dev/block/mmcblk1p2 <mountpoint>
The -o umask=0000 is essential, otherwise the permissions are rwx------; with the umask option they are rwxrwxrwx and thus can be reached.
For safety sake, mount when needed and umount promptly afterwards.
Bananiel-1944
Click to expand...
Click to collapse
dxage said:
Dear Bananiel,
your post was closest to the solution of my problem, maybe you could suggest something that will finally help me.
I've partitioned external SDcard with CWM to be used for Link2SD. Link2SD's script works fine and the EXT2 partition mounts well. The problem is with the FAT32 partition which can't be mounted by android (I get "SD card empty of file system damaged" in the notification area). When I go in CWM recovery mode I can mount that partition by choosing "mount USB storage" option and then I can see it on my PC. Partition is healthy and PC has no problems with it.
I've tried issuing commands you've suggested in your post through ADB SHELL, after that when I go to folder that I've designated as mount point I can see files from non-working partitio, but the message in notification area still persist. Also the change is not permanent, after reboot I have to do that again.
Thanks in advance for any help given.
Click to expand...
Click to collapse
In my situation (SD-card with two partitions, both vfat) the first partition automatically was mounted at start-up, the second needed to be mounted manually whenever I wanted to access it. This was also my intention as that second partition contains sensitive information.
Android has a file fstab.<system-id> in the root directory, in which some mounts are mentioned (but not all).
You could try to edit this file with the permanent mounts you are looking for. I'm not sure if that works, however, as I do not want a permanent mount.
Can you publish your results, please?
Bananiel
Finally!
I managed to get my external partitions visible with the help of this post.
Device: Samsung Galaxy Tab2 10.1
ROM: Candy5_p5110 Android 5.1.1
SDExternal: 2 Partitions; 1st VFAT, 2nd Ext3
Using Mount2Sd from Google Playstore.
I had the same mounting issues. SD external would only mount Partition 1 automatically and manually mounting Partition 2 would only be visible via Terminal.
The solution that finally fixed the invisible 2nd Partition was to reformat the 2nd Partition with Ext3 and allowing Mount2Sd to find it and mount to /sd-ext. Formatting to vfat or ext4 did not work. Only Ext3 did the trick.
I hope this helps others and big thanks to the OP for bringing this issue up.
Hi, this is a tutorial that explain how to change the internal sd with the external.
It is an idea of danitab78, i decided to create this to shy away from talking in other threads.
I think it solves the main problem of our device that has only 2,3 gb as internal sd.
It works on this script:
ICS:
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:61 /mnt/sdcard
mount -o bind /data/media /mnt/sdcard/external_sd
chmod 777 /mnt/sdcard/external_sd
The only thing to do is create a "external_sd" folder in external_sd
At first, you must have a file managar that works on rooted phones like "Root Explorer" and also "Script Manager - SManager" so you can bring the attached file into your phone, i suggest you to paste it in system/etc. Now rename your .txt in .sh.
Open Script Manager with root permissions and find the .sh, tap on it, and if is asked how to open it, choos script/executable. In the next windows tap on "su", "boot","save" and finally "run".
If it doesnt give you any error it has worked!
Congratulations
All rights reserved to Danitab78
JELLYBEAN:
I copied kumas post, so thanks to him here and here
ROOT IS REQUIRED and Jelly Bean
I made/copied (lol) this script by combining Artas182x and Mateo1111 scripts
this is how you would save it as script (.sh file)
Code:
#!/system/bin/sh
SU
busybox mount -o remount,rw /
busybox mount -t vfat -o umask=0000 /dev/block/vold/179:61 /mnt/sdcard
if busybox mount | busybox grep vold/179:61; then
busybox mount -o bind /data/media /storage/external_SD
busybox rm /storage/external_SD/external_sd
busybox chmod -R 777 /storage/external_SD
fi
Or just download the attachment and unzip to your sdcard and run with smanger or similar app (and set to boot at startup if you want)
Note:
1.When using the camera and video recorder, change settings storage to internal memory (if you don't, you will have to reboot the phone to see your pic/vid you just took)
2.This script will allow you to install large size games (ex. Asphalt 7) but you will still need link2sd (to move apps to your external_SD)
Now if you use the link2sd app, select the "create symbolic link"
lol one more thing, you will need to partition your sdcard to use link2sd.
3.If y'all have busybox installed properly this script should work fine. In addition, this script is all set for init.d (but i have problems using this method). You will get an error for SU, because it's set for init.d. However, the script still works fine through a terminal.
Warning, using Android Tuner app can mess up your L9 and I'm not responsible if you do!
Or if you don't want to use link2sd and partition your Sdcard, you can use Android Tuner However, this app is really advance and you should make a CWM backup (thanks to Artas182x) before messing with this app. It has a lot of options and you could mess the phone up.
I did it for a better english, i hope
Will it take the apps into it!?
Sent from my LG-P765 using xda premium
hkfree said:
Will it take the apps into it!?
Sent from my LG-P765 using xda premium
Click to expand...
Click to collapse
I did it and i installed NFS Most Wanted and Asphalt 7, so definetly yes
it works, my internal now states 16gb
but i still don`t understand " The only thing to do is create a "external_sd" folder in external_sd"
does it means i have make folder external_sd after all the process?
in process so should be like this
1. install script manager
2. load script
3. check internal sd now should be as big as our mmc
4. create a "external_sd" folder in external_sd
does it right?
Normally, in /mnt/sdcard there is a folder named "external_sd" that is your microsd card, you have to create a folder named "external_sd" in it.
It doesnt matter if you create it before or after the script, i did it after and it worked but i think it would have worked in any case
Perfect it worked!!!
Sent from my LG-P760 using xda app-developers app
it really is move data of the application..
but if you take a look on "/data/app/" the installed apps is still there and the "/sdcard/app" is empty
it seems move everything including data of application (OBB files), and default location of application like whatsapp media now is in the "/sdcard/whatsapp"
is that normal or there would be any possible way to move "/data/app" to such as "/sdcard/app" ??
Roker1 said:
Hi, this is a tutorial that explain how to change the internal sd with the external.
It is an idea of danitba87, i decided to create this to shy away from talking in other threads.
I think it solves the main problem of our device that has only 2,3 gb as internal sd.
It works on this script:
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:61 /mnt/sdcard
mount -o bind /data/media /mnt/sdcard/external_sd
chmod 777 /mnt/sdcard/external_sd
The only thing to do is create a "external_sd" folder in external_sd
At first, you must have a file managar that works on rooted phones like "Root Explorer" and also "Script Manager - SManager" so you can bring the attached file into your phone, i suggest you to paste it in sys/etc. Now rename your .txt in .sh.
Open Script Manager with root permissions and find the .sh, tap on it, and if is asked how to open it, choos script/executable. In the next windows tap on "su", "boot","save" and finally "run".
If it doesnt give you any error it has worked!
Congratulations
All rights reserved to Danitba87
I did it for a better english, i hope
Click to expand...
Click to collapse
Does this work without rooting your phone?
Sorry for being a noob here...just switched to android and got this phone... :silly:
sunnydsouza said:
Does this work without rooting your phone?
Sorry for being a noob here...just switched to android and got this phone... :silly:
Click to expand...
Click to collapse
nope, you must have access to /system by rooting ur phone
itoit said:
it really is move data of the application..
but if you take a look on "/data/app/" the installed apps is still there and the "/sdcard/app" is empty
it seems move everything including data of application (OBB files), and default location of application like whatsapp media now is in the "/sdcard/whatsapp"
is that normal or there would be any possible way to move "/data/app" to such as "/sdcard/app" ??
Click to expand...
Click to collapse
the script work only for swith internal sd card whit external.
No need move apk in sdcard
Roker1 said:
At first, you must have a file managar that works on rooted phones like "Root Explorer" and also "Script Manager - SManager" so you can bring the attached file into your phone, i suggest you to paste it in sys/etc. Now rename your .txt in .sh.
Open Script Manager with root permissions and find the .sh, tap on it, and if is asked how to open it, choos script/executable. In the next windows tap on "su", "boot","save" and finally "run".
If it doesnt give you any error it has worked!
Congratulations
All rights reserved to Danitab78
I did it for a better english, i hope
Click to expand...
Click to collapse
insted of script manager u could simplify this to make a script in rom toolbox lite via scripter
just put inside the script
Code:
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:61 /mnt/sdcard
mount -o bind /data/media /mnt/sdcard/external_sd
chmod 777 /mnt/sdcard/external_sd
\
name it as u wish, example "int2sd" and make it run on boot
sorry for asking this..
if i do this switching the memory, so the external sd will be the internal and the internal will be the external sd.. is it right?
bramprasetyo said:
sorry for asking this..
if i do this switching the memory, so the external sd will be the internal and the internal will be the external sd.. is it right?
Click to expand...
Click to collapse
Yes!
thanks for the script, it's working perfect
Roker1 said:
Yes!
Click to expand...
Click to collapse
thank you for quick reply...
and how to undo this script? just delete and reboot?
bramprasetyo said:
thank you for quick reply...
and how to undo this script? just delete and reboot?
Click to expand...
Click to collapse
yes
danitab78 said:
yes
Click to expand...
Click to collapse
thanks
let me try it now...
I ran the script and then went back into folder with root explorer and it looks like all the files from sd have been copied to sd_external
Sent from my LG-P769 using xda app-developers app
R: How to exchange memories
After following this guide should i See more space here? Cause i've done IT without errors but the space avaible is the Same.
Sent from my LG-P760 using xda app-developers app
it works. thanks