CWM Touch v6.0.4.7 - Xperia Z1 Compact Android Development

delete thread please!

great work thank you munjeni:good:

Great! Thanks, munjeni

Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?

Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!

New version is out! http://forum.xda-developers.com/attachment.php?attachmentid=2594573&d=1393093417

1jkan said:
Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?
Click to expand...
Click to collapse
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:

munjeni said:
Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!
Click to expand...
Click to collapse
it's look like XZ1c uses unified storage.
unified storage = intenal storage(/mnt/sdcard0/) --> /data/media
Code:
[email protected]:/storage/sdcard0 # df
Filesystem Size Used Free Blksize
/dev 343.1M 72.0K 343.0M 4096
/mnt/asec 343.1M 0.0K 343.1M 4096
/mnt/obb 343.1M 0.0K 343.1M 4096
/system 1009.3M 877.7M 131.6M 4096
[COLOR="Red"]/data 3.9G 1.3G 2.6G 4096[/COLOR]
/cache 246.2M 4.3M 241.9M 4096
/data/idd 7.5M 1.1M 6.4M 1024
[COLOR="red"]/storage/sdcard0 3.9G 1.3G 2.6G 4096[/COLOR]
/mnt/asec/com.keramidas.TitaniumBackupPro-1 2.0M 80.0K 1.9M 4096
/mnt/asec/com.mobisystems.editor.office_registered-1 50.0M 48.7M 1.3M 4096
/mnt/asec/com.quoord.tapatalkHD-2 31.0M 29.2M 1.9M 4096
/storage/sdcard1 29.7G 27.8G 1.9G 32768
[email protected]:/storage/sdcard0 #
mounts :
Code:
[email protected]:/storage/sdcard0 # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-num/p12 /system ext4 ro,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p14 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p13 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p10 /data/idd ext4 rw,nosuid,nodev,noatime,nobarrier,data=ordered 0 0
[COLOR="Red"]/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0[/COLOR]
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobisystems.editor.office_registered-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.quoord.tapatalkHD-2 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/vold/179:33 /storage/sdcard1 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
from /system/build.prop
Code:
# It is changed to true in msm8660_surf
# Change it back to false according to blue
#
# Simulate sdcard on /data/media
#
[B][COLOR="Red"]persist.fuse_sdcard=false[/COLOR][/B]
this example i take from lt26w build.prop the value should be true for XZ1c.
/init.semc.rc
Code:
# msm specific files that need to be created on /data
on post-fs-data
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
mkdir /data/media/Download 0775 media_rw media_rw
chown media_rw media_rw /data/media/Download
/init.sony-device.rc
Code:
# User 2800: sdcardd
service sdcardd /system/bin/sdcard /mnt/int_storage 2800 2800
user root
group sdcard_rw
disabled
/system/bin/sdcard --> binary to fuse mount /data/media to /mnt/int_storage
i have managed to enable unified storage on lt26w by editing the build.prop and vold.fstab.hopefully this could help with internal storage mounts on XZ1c.

Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).

munjeni said:
Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).
Click to expand...
Click to collapse
http://teamw.in/DataMedia
Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device.
Click to expand...
Click to collapse

Yes, you are right, thats not posible since partition is not fat, only in linux we can see mounted storage, but thats not what we want. Will remove internal sd in mount storage menu.

any other download link for the boot.img ? thanks

munjeni said:
Hi, here is my version of the recovery, almost full working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What working what not working:
Working:
- everything including adb and external sdcard
Not working:
- can not mount internal sdcard, but I will try to get them working soon
New feature:
- increased brightness of the recovery
- battery level (icon!) in real time
- clock (icon!) in real time
- battery charging led indicator
Changelog 22.Feb.2014 :
- redesigned
- special menu (will make them soon!)
- new font (lucida console)
How to install:
1. for locked bootloaders only:
- Our recovery is replacement for not working Philz recovery from post -> http://forum.xda-developers.com/showthread.php?t=2647480
- download zip from these post (Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip), download ramdisk-recovery.cpio.lzma -> http://munjeni.homeunix.com/ramdisk-recovery.cpio.lzma, rename ramdisk-recovery.cpio.lzma to recovery.philz.cpio.lzma, copy them to Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip by replacing file recovery.philz.cpio.lzma in zip
2. for unlocked bootloaders only:
- download boot.img from http://munjeni.homeunix.com/z1c_boot.img , reboot to fastboot, flash boot.img with fastboot, go to http://forum.xda-developers.com/showthread.php?t=2620794 and give thanks to author of the ramdisk! Thanks man! My work is only on CWM, everything other is extracted from his boot image! Boot image contain CWM + stock rom ramdisk + stock rom kernel = for stock rom 14.2.A.1.114 only!
If something is not working please let me know! Enjoy!
Click to expand...
Click to collapse
Hi, the link under 1 for downloading /ramdisk-recovery.cpio.lzma is not working, server seems to be down

Server is up again, sorry

This CWM is great. I had some issues with the other (dual boot TWRP) and installing a ROM. I have installed a ROM and run backups. Haven't had time to test restore. Well done!

munjeni said:
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:
Click to expand...
Click to collapse
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Thats a known isue on CWM recovery ! I don't think if these bug will be solved soon since recovery have no internet access to sinchronise time, so recovery can not know actual date! Maybe we can implement something for getting time from radio (not sure if it is possible).

If that's the reason, then where does TWRP get the correct date and time from because there it works?

Iruwen said:
If that's the reason, then where does TWRP get the correct date and time from because there it works?
Click to expand...
Click to collapse
Sorry I dont know, but I will look into twrp source code to get idea, have no free time for cwm, but maybe later.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Excuse me for interfering...
This date format is to sort the backups. First is year, next month and last for day.
If you are using a "normal" datestamp, your files are not listed in sequence.
So, in this case your files are always listed in a way, that latest backup is the last in row.

Related

[Q] Move /cache to /sd-ext/cache

On Desire I have rooted stock Gingerbread with a2sd. Only app data are on /data partition, but it's still not enough. So I want to move /cache to /sd-ext/cache and /system/app to /sd-ext/app-s. Then I want to flash CM7r2 hboot.
So my question is how can I do this (moving to sd-ext)?
Thank you
To clarify, you mean Dalvik-cache, not /cache?!
rootSU said:
To clarify, you mean Dalvik-cache, not /cache?!
Click to expand...
Click to collapse
no I mean /cache (the one which is on 40MB partition). Dalvik-cache I have currently moved to sd (was by default on pre-rooted stock).
I want to flash hboot with only 5MB /cache and it will not be enough for downloading some apps from market, I think...
kamelot.sk said:
no I mean /cache (the one which is on 40MB partition). Dalvik-cache I have currently moved to sd (was by default on pre-rooted stock).
I want to flash hboot with only 5MB /cache and it will not be enough for downloading some apps from market, I think...
Click to expand...
Click to collapse
Right I see.
You can either use the 06mountdl script found in many AOSP roms to bind /cache/download to /data/local/download (but that then means you have to save a portion of /data for download space) or better yet:
Fixing market downloads
If you wish to bypass the problem of the small cache partition limiting market downloads, then do the following steps:
1. Use the wonderful dsixda kitchen to unpack your boot.img
2. Edit the init.rc. In the exports section add the following:
Code:
export DOWNLOAD_CACHE /mnt/asec/download
and add the following right under the section titled "# Secure container public mount points":
Code:
# Market downloads
mkdir /mnt/asec/download 0777 root system
mount tmpfs tmpfs /mnt/asec/download mode=0777,gid=1000
This will place all market downloads into a temporary ram disk, which will be deleted upon the completion of the installation.
3. Repack your boot.img and place it in the rom.
You can see an example of an edited init.rc here:
http://wbss.ro/coolexe/Extra/init.rc
Click to expand...
Click to collapse
From Here:
http://forum.xda-developers.com/showthread.php?t=992176
and following editing 06mountdl and putting in init.d could work also?
Code:
mount -o bind /sd-ext/cache/download /cache/download
kamelot.sk said:
and following editing 06mountdl and putting in init.d could work also?
Code:
mount -o bind /sd-ext/cache/download /cache/download
Click to expand...
Click to collapse
You can try but you are already mounting sd-ext for apps2sd so it will likely make a mess of things. Adding to ram disk is by far the neatest solution.
thank you rootSU very much
No probs. Let me know how you get on.
Sent from my HTC Desire using Tapatalk
I just run a small script which binds cache to /data/market temporarily for that boot.. Same thing, but cleaner than either init.rc or init.d, and reversible instantly.
rootSU said:
Right I see.
You can either use the 06mountdl script found in many AOSP roms to bind /cache/download to /data/local/download (but that then means you have to save a portion of /data for download space) or better yet:
[/MOUNT]
This is actually good if you're running data2sd. or mount it to whatever is the mount point of sd-ext/elsewhere
Click to expand...
Click to collapse
The problem with bind if you're not using data2sd is that you are not only -15MB for usage but also -download+install. So you have 200MB /data but can only use .170. Waste. Anyone not using data2sd, RAM disk is by far the best
Sent from my HTC Desire using Tapatalk
I agree it doesn't make sense if your /data is an mtd. but I thought OP wants to use sd-ext. he can bind a sub folder of whatever mount is used for sd-ext. in that case, cache inherits the free disk space of sd-ext
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droidzone, can you please post here your script and how to use it?
thank you
Here you go
https://www.box.net/shared/zt6si0qjaz6c63z8hhz2
To run it,
From a terminal:
su
bash /sdcard/cachebooster.sh
Or run it as root in Script Manager app. (easier). Dont forget to add correct location.
If you want to make it run every time phone boots, copy it to /system/etc/init.d
So I used this part of your cachebooster.sh and I have placed it into init.d:
http://pastebin.com/tiGX7A1E
after boot, cache is on sd-ext, but market gives error 492 at download of any app.
Secondly I tried to symlink all system apps from /sd-ext/app-s to /system/app with following script:
(before executing I copied all apps to /sd-ext/app-s)
Code:
#!/system/bin/bash
rm /system/app/*.*
cd /sd-ext/app-s
filelist=`find . -type f`
for i in $filelist
do
if [ ! -e /system/app/$i ];
then
chmod 644 /sd-ext/app-s/$i
ln -s /system/sd/app-s/$i /system/app/$i
fi
done
exit 0
But it gave me a bootloop....
I think it's too much linux for me
I wanted to use Supernova 2.4 ROM at first, but with my class 6 ADATA I had terrible lags, which lead to unusable system and phone overheating. So I wanted to customize stock pre-rooted Gingerbread for CM7r2 hboot.
Hmm.. Sorry I don't know why you're getting that error. It's working fine for me. It's the only way I can download apps more than 50 MB in size. Before adding it at boot, just run it from a terminal and see what happens. Maybe it interferes with some other script on your ROM.
thanks anyway Droidzone!
Like I said, it doesnt like mounting sd-ext for cache AND apps2sd. It gets messy and doesnt work properly. I tried to get it to work properly for weeks. Init.rc or 06mountdl.
Hmm ..
Can someone get me the output of this command under a2sd+?
Code:
mount
on stock rooted GB:
Code:
# mount
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/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/mmcblk0p2 /sd-ext ext3 rw,noatime,nodiratime,errors=continue,barrier=
0,data=writeback 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:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.teamviewer.teamviewer.market.mobile-1 vfat ro,dirs
ync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.bazinga.cacheclean-2 vfat ro,dirsync,nosuid,nodev,
relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,short
name=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.stt.android-1 vfat ro,dirsync,nosuid,nodev,relatim
e,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mi
xed,utf8,errors=remount-ro 0 0
#

[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!

CWM can't mount SD

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

Easy way to swap external to internal Xperia M and install apps to sd

Easy way to swap external to internal Xperia M and install apps to sd
​
Follow The steps and enjoy
1: download Root External 2 Internal SD
2: open it and grant root access
3: go to settings
4: check the three check boxes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. click on the option which says "The orignal external mounting point"
and change extsdcard to ext_card and press ok
6. then click on the option "The ext. sdcard device acess"
and change 179:49 to 179:33 and press ok
7. go back to the main page and click "External > Internal* "
that its now u can install apps on ur sd card directly from google play
Try this
http://forum.xda-developers.com/showthread.php?t=2711280
thread its better then my thread and even works on cm11
P.S. remember to click the "External> Internal* " button everytime u restart ur phone
Thanks for share.
Is it working for M Dual?
Anyone, Please conform.
Sent from my C1905 using XDA Premium 4 mobile app
Doesn't work on XMD
Any idea?
It's so interesting but in my Xperia M, SD-Card is in /dev/block/vold/179:32, no /dev/block/vold/179:33 as in this (and other) instructions.
When i set to program 179:32 all works good.
Thanks
Pacjonek said:
It's so interesting but in my Xperia M, SD-Card is in /dev/block/vold/179:32, no /dev/block/vold/179:33 as in this (and other) instructions.
When i set to program 179:32 all works good.
Thanks
Click to expand...
Click to collapse
You talking bout M Dual?
Sent from my C2005 using XDA Premium 4 mobile app
StraightEdgeKid said:
You talking bout M Dual?
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Xperia M Single but you should go to /dev/block/vold/ (Root Explorer) and check where has been adressed your SD-CARD
P.S This metod is not great beacause this program not swap, only set sd-card as intrenal memory. Propetly internal memmory is dissapear so better is using other method.
Pacjonek said:
Xperia M Single but you should go to /dev/block/vold/ (Root Explorer) and check where has been adressed your SD-CARD
P.S This metod is not great beacause this program not swap, only set sd-card as intrenal memory. Propetly internal memmory is dissapear so better is using other method.
Click to expand...
Click to collapse
other ways not working :crying::crying::crying::crying::crying:
horamankurdish said:
other ways not working :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I see no reason why that would't work.
Have you checked where is adressed your SD card?
Pacjonek said:
I see no reason why that would't work.
Have you checked where is adressed your SD card?
Click to expand...
Click to collapse
It's 179:32.
I'd tried with other options too, with this, unfortunately not working, and reason is unknown.
Sent from my C2005 using XDA Premium 4 mobile app
StraightEdgeKid said:
It's 179:32.
I'd tried with other options too, with this, unfortunately not working, and reason is unknown.
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Download Terminal Emulator and run it.
Type:
vold
mount -t vfat -o umask=0000 /dev/block/vold/179:32 /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Click to expand...
Click to collapse
Pay attention to 179:32 or 179:33 !
Tell me if there are any errors
Pacjonek said:
Download Terminal Emulator and run it.
Type:
Pay attention to 179:32 or 179:33 !
Tell me if there are any errors
Click to expand...
Click to collapse
on dual sim not working bro i tried
horamankurdish said:
on dual sim not working bro i tried
Click to expand...
Click to collapse
But what does appear?
I don't have this phone but i try help you so what does appear (if anything) after type this?
Then reboot phone (important!), go to Terminal Emulator, type:
mount >> /storage/sdcard1/tablica.txt
Click to expand...
Click to collapse
Connect your phone to PC, open your SD Card in Windows, open tablica.txt file and copy all text to your next forum post
works, but when I go to install an application from google play says there is no space
Pacjonek said:
But what does appear?
I don't have this phone but i try help you so what does appear (if anything) after type this?
Then reboot phone (important!), go to Terminal Emulator, type:
Connect your phone to PC, open your SD Card in Windows, open tablica.txt file and copy all text to your next forum post
Click to expand...
Click to collapse
It says "no such file or directory vold /179:32"
Also tried with 179:32!
No luck at all
Sent from my C2005 using XDA Premium 4 mobile app
StraightEdgeKid said:
It says "no such file or directory vold /179:32"
Also tried with 179:32!
No luck at all
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, so please reboot device, go to Terminal Emulator and type:
mount << ext_sdcard/tablica.txt
Click to expand...
Click to collapse
It will create file tablica.txt on your SD CARD.
Please put content of this file to your next post.
Pacjonek said:
Ok, so please reboot device, go to Terminal Emulator and type:
It will create file tablica.txt on your SD CARD.
Please put content of this file to your next post.
Click to expand...
Click to collapse
Here you go.
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
none /dev/cpuctl cgroup rw,relatime,cpu 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/secure tmpfs rw,relatime,mode=700 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/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated 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
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/sdcard1 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/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/0/Android/obb 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
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Sent from my C2005 using XDA Premium 4 mobile app
---------- Post added at 07:42 PM ---------- Previous post was at 07:42 PM ----------
Sorry for just pasting them, that's because im logged in from my phone.
Sent from my C2005 using XDA Premium 4 mobile app
StraightEdgeKid said:
Here you go.
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
none /dev/cpuctl cgroup rw,relatime,cpu 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/secure tmpfs rw,relatime,mode=700 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/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated 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
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/sdcard1 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/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/0/Android/obb 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
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Sent from my C2005 using XDA Premium 4 mobile app
---------- Post added at 07:42 PM ---------- Previous post was at 07:42 PM ----------
Sorry for just pasting them, that's because im logged in from my phone.
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Android 4.2 has introduced a changes in addressing the memory card. That explains all.
Please try this:
su
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
Click to expand...
Click to collapse
Pacjonek said:
Android 4.2 has introduced a changes in addressing the memory card. That explains all.
Please try this:
Click to expand...
Click to collapse
Tried till emulated, it says mount:device is busy.
And when tried all the script, it say like.
"ld/179:33 /mnt/shell/emulated <
mount: Device or resource busy
ted mount -o bind/data/media/0/storage/sdcard1 <
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Sent from my C2005 using XDA Premium 4 mobile app
StraightEdgeKid said:
Tried till emulated, it says mount:device is busy.
And when tried all the script, it say like.
"ld/179:33 /mnt/shell/emulated <
mount: Device or resource busy
ted mount -o bind/data/media/0/storage/sdcard1 <
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Sent from my C2005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try:
su
vold
mount -t vfat -o umask=0000 /dev/block/vold/179:33 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
Click to expand...
Click to collapse
In the second line there is a space! ...media/0 SPACE /storage...
its required to do root my device
or it will work only uprooted device

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