CWM can't mount SD - T-Mobile, Samsung Galaxy SIII

I just rooted my phone and installed CWM. When I try to install a zip from SD it says "E: can't mount SD" i've tried everything (manually mount SD card and format external card from CWM and phone and nothing happened!) does anybody now a solution? can I installa a ROM from internal memory? i guess i can't...
thanks a lot!

http://www.youtube.com/watch?v=JmvCpR45LKA

sswb27 said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I checked other posts and no solution for me...
thanks anyway

Download rom manger from play store and use it to update CWM.

sswb27 said:
Download rom manger from play store and use it to update CWM.
Click to expand...
Click to collapse
Thanks. I have updated it but the problem persists

Have you tried twrp recovery? If nothing else use internal storage.

Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.

dasgh said:
Your SD card is most likely formatted in exFAT filesystem. This is a MS proprietary format that requires licensed drivers to mount. As of now there are no custom recoveries that can mount exFAT.
There are a few options:
1) Re-format the card to FAT32 and do backup.
2) Get a smaller (8-16gb) card to use for backups and keep in FAT32 format.
3*) Partition larger card (32-64gb) with multiple partition types. ex. 40gb exFAT/24gb FAT32. *Please note that I have not tried this nor seen it done but just an idea I wanted to try out to see if it was feasible. I may have time to give it a shot later today and if so I'll update this post.
Click to expand...
Click to collapse
Do not partition a 64 GB micro SD to FAT32. Performance will be awful because of the way the mem blocks are sized.
Also, your internal SD is exFAT... that is read by the recovery perfectly fine.
I would say save yourself some trouble and just find a ROM kernel combo that supports exFAT micro SD. Your 64 GB will work flawlessly and performance will not take a hit.

maybe post in correct forum for more replys, just sayin

Just for anyones future reference:
This is from stock JB GS3.
Below you can see the various partitions file system types. Mostly ext4 and various ramfs types. At the bottom you can see the external storage as exfat.
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:97 /storage/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
I currently understand the recovery image to work as below. Someone please correct me if it's incorrect.
While the kernel does support exfat the "interpreter" (driver) and custom recovery image can not talk to each other. The exfat driver can only be called/read if you know which system calls to use and how to interpret its response. The custom recovery image does not know how to utilize the exfat driver.

Please read forum rules before posting
Development is ONLY for developers to post release threads
Questions go in Q&A
Thread moved

Related

[Q] Heeelllpppp sd

Total SpaceA few weeks ago I have a problem with memory SD
when I install any version (JPU, JPI, or JPY) but when boot on the
Android Sytem recovery <3e> displayed the following message:
update,media, please wait
E:can't mount /dev/block/mmcblk0p1
(no sucho file or directory)
E: copy_dbdata/media:Can't mount SDCARD:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
After that flash with ODIN and speedmod-kernel-k12k-500hz
Then the phone starts NORMALLY, but it shows me two pop up:
Preparing internal SD, SD CARD IS DAMAGED, after that I go to:
SETTING/SD card and phone storage and shows me:
SD card and phone storage
Total Space
00
Available Space
00
Unmount SD card
Format SD card
Internal SD card
Total Space
Unavaible
Available Space
Unavaible
Format SD card
Format (erase) the SD Card
Internal phone Storage
Available space
00b
So I try to format both SD card, and nothing happens.
Connect the phone to pc, open SuperOneClick v1.91 and click ROOT
Width the phone rooting i go to adb :
c:\Program Files (x86)\Android\android-sdk\platform-tools\
1____I first put the phone in Debbuging mode,
2____Second fixed if the phone is attached:
adb devices >>>
List of devices attached
100012044e6e device
3____Go to adb shell> su > mount, and show me:
# mount
mount
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#
In this case try to find a route to the internal and external sd:
external : /dev/block/vold/179:9
internal: ????????????????
I add to this thread, images with different situations.
I read the following post but to no avail:
http://forum.cyanogenmod.com/topic/6...ernal-storage/
And millions of post that talk of SD brick
PLEASEEE HELLPPP MEEE!!!!!!!!!
Read allgamer's sticky.
Insanity cm - superaosp kernel.
This question should be in Q&A, please contact moderator to get it moved also watch this
http://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player
Insanity cm017/glitch v10c

[GUIDE] Mass Storage

If you aren't satisfied with transferring files over MTP for whatever reason, I have done some digging and managed to get mass storage working for the external sdcard.
I developed some scripts for switching to and from mass storage, using posts for the GT-I9300 and for the Xperia S. You can unzip them (attached) to the root of your internal sdcard. You can then easily import them into GScript Lite, available for free through the Play store.
For reference, the commands are as follows:
Mass Storage:
Just plug in your phone and run:
Code:
echo 0 > /sys/devices/virtual/android_usb/android0/enable
umount /mnt/extSdCard/
echo "mass_storage,adb" > /sys/class/android_usb/android0/functions
echo "/dev/block/vold/179:97" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo 1 > /sys/devices/virtual/android_usb/android0/enable
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
MTP:
Unmount/Eject in your operating system first, to be sure. Then:
Code:
echo "" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo 0 > /sys/devices/virtual/android_usb/android0/enable
echo "mtp,acm,adb" > /sys/class/android_usb/android0/functions
echo 1 > /sys/devices/virtual/android_usb/android0/enable
vold
Notes:
/sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file seems to be prepared for the internal sdcard, but I have had no success in using it in conjunction with the device, /dev/block/vold/179:96. At least the external works.
and it stays without having to continually type all that?
B-Naughty said:
and it stays without having to continually type all that?
Click to expand...
Click to collapse
If you stop after the first script, unfortunately it's not going to remount the external sdcard. This does not enable a convenient UI toggle like you might have seen on other ROMs.
I recommend saving the first sequence of commands as "Mass Storage.sh" and the second sequence as "MTP.sh". You can copy them to /sdcard/gscript/ and load them into GScript Lite as new scripts. Then it's easy to activate mass storage and deactivate it at the push of a few buttons. (GScript Lite seems to crash on me after running the scripts, on exit, but to no ill effect.)
Any way to get this into an app?
jiggytom said:
Any way to get this into an app?
Click to expand...
Click to collapse
Someone could develop a specialized app, but I recommend trying GScript Lite in conjunction with the attached scripts.
thanks for the tutorial.
Woohoo!! Thanks so much for figuring this out.
[I'm having to explicitly remount the external card in the MTP script:
mount -t exfat /dev/block/vold/179:97 /mnt/extSdCard
and mount doesn't seem to be happy without an explicit type - any way around that?]
plaut said:
I'm having to explicitly remount the external card in the MTP script:
mount -t exfat /dev/block/vold/179:97 /mnt/extSdCard
and mount doesn't seem to be happy without an explicit type - any way around that?]
Click to expand...
Click to collapse
That's interesting. I didn't encounter that issue. The only difference I'm aware of is that I reformatted my card using mkfs.vfat, but you could try appending the following to the MTP script, and see if it works equally well:
Code:
vold
The whole script would become:
Code:
echo "" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun_ex/file
echo 0 > /sys/devices/virtual/android_usb/android0/enable
echo "mtp,acm,adb" > /sys/class/android_usb/android0/functions
echo 1 > /sys/devices/virtual/android_usb/android0/enable
vold
If that doesn't work, your solution might be the best one for now. Let me know if this works. I don't see any harm in adding the line, in any case.
Yes, that works - thanks again!
Just.. Perfect!!
Well, works well at home on w7 but the Xp at work doesn't want to play.
VZW SGS3 Tap a Talk
vudugan said:
Well, works well at home on w7 but the Xp at work doesn't want to play.
Click to expand...
Click to collapse
If you can install drivers at work, check the directory thread. Or, just download the Samsung SGH-I747 USB Drivers. If you can't install drivers at work, then you may be out of luck.
It would be really great to make this into an app with a widget. Really great.
Is there any reason that this would not work on a T-999?
bazald said:
If you can install drivers at work, check the directory thread. Or, just download the Samsung SGH-I747 USB Drivers. If you can't install drivers at work, then you may be out of luck.
Click to expand...
Click to collapse
I actually got it going by uninstalling the drivers, deleting Samsung folder, reboot PC . Plugged in phone, it installed drivers from there. Funny thing, after drivers installed, prompt popped up, selected view folder and wala. Weird I didn't have to run script again before the prompt.
VZW SGS3 Tap a Talk
jeffreii said:
It would be really great to make this into an app with a widget. Really great.
Click to expand...
Click to collapse
Not to say a dedicated app wouldn't be an improvement, but GScript Lite provides the ability create widgets to run different scripts. You could have one to switch to Mass Storage and another to switch back to MTP. I actually had that setup for a while, but decided I'd rather have to go through an extra couple of steps than risk running the scripts by accident.
I have made an app for the purpose. It is still in alpha stages
http://forum.xda-developers.com/showthread.php?p=29606833#post29606833
USB mass storage drive trick
BooM there it is! sweet, and thank you very much.
If Windows fails to find the correct driver, go to the Device Manager and manually set it to use the driver, "USB Mass Storage Device". It seemed to try to stick with the MTP driver in my case.
I succesfully used this script here to swap internal and external sd cards. Now I want to mount the formerly internal sd card. This should be possible as it is now booting from the external card.
I tried the following but it is not working. Any ideas? umount /mnt/extSdCard/
echo "mass_storage,adb" > /sys/class/android_usb/android0/functions
echo "/dev/fuse" > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file
echo 1 > /sys/devices/virtual/android_usb/android0/enable
here are my df results - you can see that the sd cards are switched:
[email protected]:/data/data/com.teslacoilsw.quicksshd/home # df
Filesystem Size Used Free Blksize
/dev 829M 84K 829M 4096
/mnt/asec 829M 0K 829M 4096
/mnt/obb 829M 0K 829M 4096
/system 1G 1017M 436M 4096
/data 12G 319M 11G 4096
/persist 7M 4M 3M 4096
/cache 826M 14M 812M 4096
/efs 13M 4M 8M 4096
/tombstones 7M 4M 3M 4096
/firmware 63M 42M 21M 16384
/mnt/sdcard 29G 16M 29G 16384
/mnt/extSdCard 12G 319M 11G 4096
/data/internal_sd 12G 319M 11G 4096
/mnt/sdcard 29G 16M 29G 16384
/mnt/extSdCard 12G 319M 11G 4096
Here is dump of my mounts file:
# cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,jo urnal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p16 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier= 1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1, data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,da ta=ordered 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barri er=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,a llow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remoun t-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id =1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatim e,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=c p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /data/internal_sd fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,gr oup_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/sdcard vfat rw,dirsync,relatime,uid=1000,gid=1023,fm ask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortnam e=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /mnt/extSdCard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group _id=1023,default_permissions,allow_other 0 0
[email protected]:/data/data/com.teslacoilsw.quicksshd/home #
Any suggestions?
There is an app originally developped for i9300 but it definitely works on I747(M)
:good:This solution works elegantly - read my comments regarding the very few existing hiccups.
Tested on I747M - Rogers/Bell/Virgin - stock ROM, rooted
To Member - OP, the original poster of this thread: please understand that while your efforts are appreciated, I have posted this link here in order to avoid confusion by creating another similar thread. NO offense intended whatsoever - I just wanted to share and help. Thank you for understanding!

[Q] Where do I find a 2nd SDcard partition?

Hi,
I formatted my external SDCard with 2 partitions, so I could use it with Link2SD. Since I am on a Mac I only could format the first one, which is FAT32. Now I need to format the 2nd with ext4 but I can only do this from inside the phone. Which is no problem, except I do not understand where I can find the device, I need to format. So, to sum it up: I have already a 'linux' type partition on the SDCard, unformatted, however. And I have a FAT32 partition on it, which gets mounted by Android already. What do I need to issue to the mke2fs command as input?
This is what I get, when issuing 'mount'.
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=771,uid=1000,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:32 /mnt/emmc vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:66 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:66 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ $ ls /mnt
asec
emmc
obb
sdcard
secure
[email protected]:/ $ ls /dev/block/vold/
179:0
179:1
179:10
179:11
179:12
179:13
179:14
179:15
179:16
179:17
179:18
179:19
179:2
179:20
179:21
179:22
179:23
179:24
179:25
179:26
179:27
179:28
179:29
179:3
179:30
179:31
179:32
179:4
179:5
179:6
179:64
179:65
179:66
179:7
179:8
179:9
[email protected]:/ $
In the recovery under mounts or advanced
Sent from my One V using Tapatalk 2
Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.
zmix said:
Thank you, I tried that first. But that does not help, since I have cwm5 installed, and that only formats up to 4GB. I need to know where I can find it in the /dev directory, so I can issue the path to mke2fs from 'adb shell'.
Click to expand...
Click to collapse
you sure??? i've formated my 8GB one with CWM5 before.....try TWRP or CWM6
Could be, that it offers 8 GB as well. I don't remember. But this is a 32GB card I have in use. What I'd need is two primary partitions, one around 6-8GB/ext4, the other one takes the rest as FAT32.
Can I install a different recovery mod, without resetting/erasing the phone? Is it as simple?
Ok, I updated CWM to v6 and re-checked. The max size is still 4096. Also I noted this:
After I left "advanced/partition" and turned on the log this shows up each time I select "show log"
Code:
When opening the log I get I: Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblkp1
and the "advanced/partitions" menu item is gone. "parted" in normal boot said, that I have overlapping partitions on the sdcard, which I doubt, since I did the partitioning with a special partitioning utility. Anyways, going to boot up a Linux VM now, should have done so much earlier It's just always so messed up with getting external volumes on USB to recognized.
I'll sort this ASAP thank you for bringing it to my attention
Sent from my One V using Tapatalk 2
Thanks for trying so hard. Greatly appreciated
On a side-note... I tried with a VM, but whatever way I tried to connect the SD card to the Linux guest, I did not succeed. So I am here again, no way to create an ext4 filesystem from inside the phone. Currently I play with the thought about installing a minimal, chrooted debia in my phone. But then I still have the problem with parted moaning about "overlapping partitions", which must be invisible to me, since I just checked the partition table with OS X' fdisk and all numbers seem in sequence. Okay, going to the other thread

data2sd: Can't umount /data: Device or resource is busy

Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).
Chickenmarkus said:
Hello,
I want to use data2sd for my WFS but it doesn't work. It hangs on the white HTC bootscreen.
Over the ADB shell I saw the problem that the internal /data-partition is still mounted. But the external /data-partition is mounted too!
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /devlog yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /system/data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nouser_xattr,commit=50,barrier=0,data=ordered,noauto_da_alloc 0 0
In this configuration ls /data lists the files moved from the data2sd installer script. After umount /data only the intertnal /data-partition is mountet and ls /data lists only the things the data2sd installer script leave like "dalvik-cache".
So the data2sd script should work. But the problem is that the internal /data partition isn't unmounted while booting I think.
How can I fix this?
Bye Markus
PS: I use the chucky-ROM (now links allowed for new users).
Click to expand...
Click to collapse
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.
crossfire77 said:
which rom you exactly use?is it based on stock ? and you can try with ext3 partition.
Click to expand...
Click to collapse
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.
Chickenmarkus said:
I try to masquerade the link that the forum software doesn't detect it as link: www . htcmania . com/showthread.php?t=460658
This one works fine for other devices of other persons - also with data2sd.
If I mount the Ext4-partition on another point I can use it without any problems.
With another data2sd script based on ext3 there is the same issue.
Click to expand...
Click to collapse
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Sent from my HTC Wildfire S A510e using Tapatalk 2
crossfire77 said:
Im not sure about data2sd scripts but you can try alternate scripts like int2ext+,int2ext4+ or a2sd+
These all are pretty new and fast..
Click to expand...
Click to collapse
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:
Chickenmarkus said:
A2sd work how it should but is not that one I want. The same with Link2SD.
I didn't try the int2ext4 script but it had a good idea: Instead of unmounting the internal /data (where it hangs because of business) and mount it somewhere else, the better way is to move it with "mount --move" directly to the new place. After changing this in the data2sd script everthing works great now!
Thanks for this hint. :good:
Click to expand...
Click to collapse
i guess a2sd+ works same as link2sd.it will mount downloaded apps,dalvik cache and cache to sd-ext.system will remain untouchable.
read this here

SM-T310 Swap ExternalSD to Internal

Original thread can be found here.
Credit to :
xalien8dx
mattiadj
I have modified this script to work with the SM-T310. If you want it to work on other Tab 3 models you will need to provide me your external sd card device node.
Follow instructions in the quoted text below using the script attached to this post.
Here's a script I modified originally its a script written by mattiadj so I gotta give him props
Here's his thread its for the Galaxy S III I think - http://forum.xda-developers.com/show....php?t=1772234
This will make your external SDcard as Internal and your Internal SDCard external
It mounts data/media to your extSdcard
Please make a backup before you do this, just in case.
Let me know if you have any problems
1. Anyway.. you will need to place this script in your /data folder (Yes you need to be rooted)
2. Next use ES file manager and give it 777 permission (For the non-linux users, that's full permission on it, Read, write, execute for just user)
-----------------to do this with ES file manager just press and hold down on the file and look at its properties. At the bottom you can see Permissions, hit the Change button and check-mark everything for user
3. Use Smamager (Download it if you dont have it, ... .its free) and goto the script file and open as script/execute, then when it opens choose "Is executable" and then click "Su" & "Boot". Click "Save".
4. Reboot and enjoy.
To go back to the normal setup just delete the script or open it back up in smanager and clear the SU & Boot options.
In order for some apps to function properly you will have to copy some folders from your old internal sdcard to your "New" one.
For example.. aptoide wouldnt work until the aptoide repos folder was copied over. If you want you can just copy over everything to be safe. I on the other hand just picked and chose what I needed
Click to expand...
Click to collapse
Finding Device Node
1. Run "mount from terminal emulator. The out put should look similar to the following:
Code:
127|[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/platform/dw_mmc/by-name/SYSTEM /system ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/dw_mmc/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/platform/dw_mmc/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/platform/dw_mmc/by-name/USERDATA /data ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[B]/dev/block/vold/179:17 /mnt/media_rw/sdcard1 vfat[/B][/B]rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
2. The bolded line is what is needed from other devices /dev/block/vold/179:17 /mnt/media_rw/sdcard1 vfat.
can you edit it for the 210 r which is 179:73 thanks a ton
khudson said:
can you edit it for the 210 r which is 179:73 thanks a ton
Click to expand...
Click to collapse
Untested so your device might be consumed by the Banefire, but find attached the script requested with the appropriate change.
did it work?
zibrah3ed said:
Untested so your device might be consumed by the Banefire, but find attached the script requested with the appropriate change.
Click to expand...
Click to collapse
did this work for the SM-210?
i feel like im doing somthnig wrong
Hey,
So i think im doing somthnig wrong, i have Smanager and placed the file in root data. Ran the script, then whenever I try to reboot my sm-t210r device the screen does not turn back on and i need to reformat, ive tried this script and also the original script but changed it to 179:73 both did same thing. I feel like im missing somthing but idk what
defleshed2 said:
Hey,
So i think im doing somthnig wrong, i have Smanager and placed the file in root data. Ran the script, then whenever I try to reboot my sm-t210r device the screen does not turn back on and i need to reformat, ive tried this script and also the original script but changed it to 179:73 both did same thing. I feel like im missing somthing but idk what
Click to expand...
Click to collapse
Possibly dumb question but is your external sd formatted as vfat?
will try tonight
thanks i will try tonight!
zibrah3ed said:
Untested so your device might be consumed by the Banefire, but find attached the script requested with the appropriate change.
Click to expand...
Click to collapse
sc card
zibrah3ed said:
Possibly dumb question but is your external sd formatted as vfat?
Click to expand...
Click to collapse
my sccard is exFAT
zibrah3ed said:
Possibly dumb question but is your external sd formatted as vfat?
Click to expand...
Click to collapse
one of the lines say mount -t vfat -o umask=000 /dev/block/vold/179:73 /mnt/sdcard
i think mines a exFAT 64g would that effect it? does my sdcard need to be reformated to vfat?
Hi!
defleshed2 said:
one of the lines say mount -t vfat -o umask=000 /dev/block/vold/179:73 /mnt/sdcard
i think mines a exFAT 64g would that effect it? does my sdcard need to be reformated to vfat?
Click to expand...
Click to collapse
my english is very bad.i can't understand forum topics.
my SM T210 7.0 how swap memory?
sorry for english
Exfat and vfat are the same for system type no need to reformat your card.
This script is known to work on the 310 (8" WiFi only). At this point the 210 version (7") apparently does not work. The banefire burns strongly.
The script allows the external SD card to be used in place of the internal SD.
sent from a buggy xda app by some miracle
Does this work for T210?
Please make an test version for it atleast.
any way to get this to work on t211 ?

Categories

Resources