I'm using the MerrukTechnology Kernel 2.0 PRE-FINAL (2.6.35.7 [email protected]), Android Version: 2.3.6, Base Version: S5360BUTLC1, ext4 partitions, tried Darktremor app2sd, custom made (http://forum.xda-developers.com/showthread.php?t=832799), and etc.
Nothing works right, i used this custom on my G5 and works Just fine.
But on SGY not works well, sometimes works, sometimes not, sometime works and on next reboot stop, even can mount ok but apps not works.
Sometimes works perfect, but when i restore my Titanium backups, on next restart stop working.
This is the Script i'm trying:
/system/etc/init.d/02app2sd:
PHP:
#!/system/bin/sh
LOG=/data/app2sd.log
echo "$(date) mounting..." > $LOG
mount -o rw -t ext4 /dev/block/vold/179:2 /sd-ext 1>>$LOG 2>>$LOG
mount -o rw -t ext4 /dev/block/mmcblk0p2 /sd-ext 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/app /data/app 1>>$LOG 2>>$LOG
mount -o bind /sd-ext/dalvik-cache /data/dalvik-cache 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
I already tried almost everything, somebody know some working script?
and what your log said?
irfanbagus said:
and what your log said?
Click to expand...
Click to collapse
pastebin.com/bih8vtiU
I wipe, i put script, restore backup and next restart stop all stop work even logcat said waiting device!
And app2sd.log:
# cat /data/app2sd.log
cat /data/app2sd.log
Tue May 15 15:40:26 BRT 2012 mounting...
mount: Device or resource busy
rootfs / rootfs rw,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437
0 0
/dev/block/stl11 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=or
dered,noauto_da_alloc 0 0
/dev/block/stl10 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=o
rdered,noauto_da_alloc 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /merruk tmpfs rw,relatime,size=32k 0 0
/dev/block/vold/179:2 /sd-ext ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/app ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:2 /data/dalvik-cache ext4 rw,relatime,barrier=1,data=ordered
0 0
Tue May 15 15:40:29 BRT 2012 mount finished
Click to expand...
Click to collapse
you can try repencis. it has a2sd support but you'll need to change your partition into ext2.
kurotsugi said:
you can try repencis. it has a2sd support but you'll need to change your partition into ext2.
Click to expand...
Click to collapse
I don't like custom themes
I tried the DarkTremor too, but stops working too.
you can replace the theme with stock one. the one you need is the a2sd script in /system/bin and /system/xbin. everything else could be replaced with stock rom.
Not works anyway, even i tried the ChobitsDigitalis and i wipe, flash and when reboot it show the stock room not the custom rom
nexbr said:
I don't like custom themes
Click to expand...
Click to collapse
Try terma kernel but make sure a2sd script install 1st b4 the kernel.
Actually u can custmz ur stok kernel so can run a2sd.
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!
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