Develop Bugs

data2ext for HTC Hero & G2 Touch

Hi!
I was experimenting with the data2ext script made for the Desire in following thread:
http://forum.xda-developers.com/showthread.php?t=859419
Now I managed to get it working with HTC Hero and Flykernel12a and Amon RA-s recovery v1.7.0.1 .
MAKING THIS WORKING IS A RISKY OPERATION! DO NOT START IF YOU DO NOT UNDERSTAND WHAT IS WRITTEN BELOW! I'M NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE OR YOU LOOSE YOUR DATA!
So here is what I made:
- make backup of your entire SD card, because we are going to repartition it, so all data will be lost on your SD card
- reboot to recovery and MAKE NANDROID BACKUP of your existing configuration!!! Then stay in recovery mode, and copy your NANDROID BACKUP to a safe place on your computer from the SD card!!!!! DURING THE OPERATION WE WILL ERASE THE WHOLE SD CARD!!!
- wipe your cache and dalvik-cache (only this 2, NO factory/data reset!!)
- connect to your phone with "adb shell" (while in recovery!!)
- in the shell execute following commands:
(do this only if you have active app2sd and your app/app-private/dalvik-cache directories are on the SD card EXT partition)
mount /data
rm -rf /data/app
rm - rf /data/app-private
rm - rf /data/dalvik-cache
mkdir /data/app
mkdir /data/app-private
mkdir /data/dalvik-cache
chmod 777 /data/app*
chmod 777 /data/dalvik-cache
chown 1000:1000 /data/app*
chown 1000:1000 /data/dalvik-cache
- now we will copy back the apps on the nand
mount /sd-ext
cp /sd-ext/app/* /data/app
cp /sd-ext/app-private/* /data/app-private
(no need to copy the dalvik-cache content!)
umount /sd-ext
- so now we have all our app on the nand again. next step is to put the 04data2extV4 script into the right place
umount /data
mount /system
exit
(now leaving shell to copy file)
in the command prompt execute:
adb push pathtothescript/04data2extV4 /system/etc/init.d/
adb shell
(back to shell again)
chmod 755 /system/etc/init.d/04data2extV4
chown 0:2000 /system/etc/init.d/04data2extV4
rm /system/etc/init.d/05mountsd
(remove script which mounts SD card differently)
rm /system/etc/init.d/10apps2sd
(remove script which makes app2sd)
umount /system
exit
(now leaving shell)
now we have to repartition your SD card to 2 ext and 1 fat partition. For this use the utility1 I uploaded which is modified version of the original utility in /sbin.
in command prompt:
adb push pathtoyourscript/utility1 /sbin/
adb shell
(back to shell)
chmod +x /sbin/utility1
(now execute the utility)
/sbin/utility1
choose 0 from menu: Partition SD 2 EXT 1 FAT (can set sizes)
enter the first EXT partition size (min. 3-400, I use 1300 - values are in MB)
enter second EXT partition size (min. 2-300, I use 300 - values are in MB)
the rest will be configured for the FAT32 file system
On the first EXT partition you will store the whole /data
On the second EXT partition you will store the /data/data in a loop file
Now we are hopefully ready to reboot, the rest will be managed by the 04data2extV4 script, wich creates the ext2 file systems, converts them to ext4, stets file system option such as journaling where needed, etc and copies everything from nand to ext4.
I hope this works for all. I reached Quadrant score for total system score about 455, without data2ext I had about 400. But I have a Class4 SD card. On class6 I'm sure it will be even faster.
Again, it is risky, so take care.
The boot process can be long, because at the first time it will copy the whole /data directory to the first EXT partition, the data/data directory on the 2nd partition, and will recreate the whole dalvik-cache (remember we wiped!).
Enjoy
Regards,
byr2
PS: in the RAR file you will find an FSTAB file. I removed the /sd-ext mount option from it. If you have trouble, try to replace the fstab file in /etc to this fstab file or remove the /sd-ext mount option from your fstab

Thank you for this.
Just a few questions. The EXT partitions, are they EXT 2, 3 or 4?
Are you using exactly the same script as ownhere? As in, you use exactly his method, aka the following one:
"I would like to share my Data2EXT script, a collection of data2sd(Thanks to sibere) and the advantages of ext4, you can let the phone run at peak efficiency.
I use EXT4 for whole SD 2nd partition, and create a ext2 loopback device with 1/5 size of 2nd partition.
The files in /data/app,/data/.systemapp it not updated frequently. so store them in EXT4.
In /data/data and /data/app-private, a lot of small files and sqlite database, is updated frequently. so store thenm in EXT2 loopback device.
/data/dalvik-cache is stored in phone memory /mnt/asec/mtddata for distributed IO pressure.
/data/misc, /data/system, /data/property is stored in phone memory /mnt/asec/mtddata for system settings restore(or you will lost your timezone/language settings after reboot).
use this script, I can get quandrant score:2000+, IO:4000+, my phone is smooth and quickly."
Are you running this stable? Reboots? All apps show after reboots?

Hi!
The two EXT partition is EXT4 partition. The script I provided is based on ownhere's script, wich is modified only in a few places.
For example on hero I do not have a /system/xbin/mkfs.ext4 like he had, but only a mkfs.ext2, so I have to create the EXT4 partition on a different way. Also the loopback device is set up in a different way than in the original script.
But what you quoted remains so, which means I did not modified any location of storage files, nor did modified filesystem parameters. First EXT4 ha no journaling ,second EXT4 has journaling, ext4 loop device has no journaling.
You can diff the two scripts to see the difference, but an example here:
Original part:
/system/xbin/mkfs.ext4 -b 4096 -m 0 -F -L userdata /dev/block/mmcblk0p2
/system/bin/tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
/system/bin/e2fsck /dev/block/mmcblk0p2
/system/bin/tune2fs -O ^has_journal /dev/block/mmcblk0p2
Modified part:
/system/xbin/mkfs.ext2 -b 4096 -m 0 -F -L extdata /dev/block/mmcblk0p2
/system/bin/e2fsck -y -v -f /dev/block/mmcblk0p2
/system/bin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/system/bin/e2fsck -fpDC0 /dev/block/mmcblk0p2
/system/bin/tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
/system/bin/e2fsck /dev/block/mmcblk0p2
/system/bin/tune2fs -O ^has_journal /dev/block/mmcblk0p2
As you can see I create an ext2 partition, check it, and with tune2fs I convert it to EXT4, check it again, and set the same parameters ownhere has set.
for loopback device I use:
$BUSYBOX losetup /dev/block/loop1 /mnt/asec/extdata/ext4
$BUSYBOX mount -t ext4 -o loop,sync,commit=3,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/loop1 /mnt/asec/tmpdata
the losetup is needed, because for some reason it won't mount as loop. But this way it is working.
Other parts of the script are untouched.
Regards,
byr2

"Are you running this stable? Reboots? All apps show after reboots?"
Till now everything runs OK, no reboot, all widgets, apps, settings were preserved. After reboot also everything OK. Made some phone calls, no problems so far.
Just with Class4 SD card the speed gain is not as huge as expected. The IO performance is slightly better, but not too much. I've read posts on CDMA Hero forum, where they managed to get quadrant score over 700, but I'm sure not with a Class4 SD card
But the funniest thing in settings is: Available internal phone storage: 1,17Gb

Excuse me for the noob question, but what this process basically does is make the entire phone run off of an ext4 partition on the SD card?

No, not the entry phone, just the /data directory is moved to ext4 partition (wich is accessed frequently by the OS, and where applications and application related data are stored). The kernel, firmware, etc. remains on the NAND.

I wonder what one does when flashing a new ROM =/ You have to go through this procedure every single time? What does AmonRA do when you Wipe Data/Factory Reset?
So essentially the differentiations are due to the fact that we lack a /system/xbin/mkfs.ext4 (since we only have an ext2) and you turn the first EXT4 partition into a non journaling one to fill the lack of that, if i understand correctly.

If you flash a new rom, then all this is gone, since if will overwrite the /system/etc/init.d where our data2ext script is located. So you're right, you have to do this every time you flash a new ROM. A solution would be to pack this script into the ROMs, so it would work out of the box without this hack mentioned in the first post.
The data/factory reset wont work I think, because it deletes from the nand, but since our data/settings are not on the nand but the SD, it will have no effect.
the first ext4 partition is non journaling because ownhere write the script so. You can read in his post why he choosed to do so.
The first EXT pratition where /data is stored is a EXT4 part without journaling
The second EXT partition where the loop file is stored is an EXT4 part with journaling
and the LOOP file which contains an EXT4 partition without journaling
from ownhere's post:
"EDIT:2010/12/12 update V4 script:
/data/:ext4, disable journaling
/data/data:ext4 loopfile on ext4 device, enable journaling on ext4 device, disable journaling on ext4 loopfile, for fast and stable sqlite3 access.
really smooth this time. please trying..."
This is the setup here also.
byr2

I see, the script is essentially the same, with your own critical changes to fit the Hero.
Now what i am trying to understand is what happens when you want to flash a new ROM.
Say you place the 04data2extV4 script in the new ROM's /system/etc/init.d and remove the other two scripts if they exit (05mountsd and 10apps2sd). Does this mean the partitions and this whole process won't have to be repeated?
Also when installing a new rom it is recommended you wipe data and system, if AmonRA doesn't wipe, what do we do?

Well, I've not tested to install a new rom, but let think:
- the partitions are preserved on your SD, so repartitioning is not needed.
- but as you mention all data/settings are currently on your SD, so a wipe does nothing with it, and if you simply put the 04data2extV4 script back to init.d I think it will mess things just up... but if you just delete everything off the two EXT partitions I think it will be fine

That's the only limitation i have so far as to not attempting this.
I wonder if i can mod the AmonRA Recovery to delete the content of those 2 partitions instead =/
I'm going to have a look.

Nice work!
By the way, I was thinking. Why not just make an ext partition, add a line for it in fstab and set the mountpoint for it to be /data. What would happen if I tried this?

Byr2.... just wanted to say this is first thing i read today and without coffee all I heard was
Blah blah blah dangerous blah blah blah faster blah blah risk blah blah even faster
Lmao
Once I get my head working it should prove interesting though
Thanks for this experiment
Sent from my HTC Hero using Tapatalk

ok, sitting down at pc now, drinking espresso...
this is starting to sink in
Instant benefit is huge storage space which, coupled with the method used, ought to have a general performance improvement over previous ext-based apps2sd, right? if so then removing ext-based apps2sd and using this script concept instead seems like a good plan if, for example, every rom builder switched to this concept and removed old apps2sd stuff simultaneously. Does that sound right or wrong?
if you have a fast sd card then the speed benefit should be very good, better than using ext-based "apps2sd" since it's the actual data partition on the ext card.
and I too would like to know the answer to the brief question someone already asked - what about just setting a mount point to data on the sd card and doing it that way in simple linux fashion? I'm not bothering to think this through - coffee's still kicking in - I'll leave the intelligence to you folks who are already awake.
IMHO this idea of yours is quite brilliant as a goal (well ok, it's not your idea, but you did it first on the gsm hero . The thing that slows my phone the most is reads and writes to phone memory and to my stock sd card. I can upgrade the sd card but the phone memory writes are still slow. This would improve the speed of the largest file writes when managing my apps and installing from the market which we all know brings our phones to a standstill briefly during installs and so on.
How's the performance when installing apps? does your phone still crawl for a bit at those crucial moments or is it all somewhat less of a dramatic slowdown now?

Hi All!
Well, If you do not change the ROMs frequently, it should not be a problem that ROM developers do not include this script. However till now only one ROM developers have taken care about this opportunity, I think it was Cronos. They have a modified ROM wich supports this kind of functionality.
The speed gain over app2sd comes from storing the whole data partition on a faster SD card than the internal NAND. As my tests show a class4 SD card is slightly faster than the internal NAND (not much, say about 5-10%). A class6 SD card could be much more faster. All application access the data partition to read and write settings/data. Even the Frimware stores things there, so if you have a fast SD card, overall system performance could be great.
Not to mention about stored data space. With app2sd you only store the downloaded apk-s on the EXT. With data2ext you have extra space for the application data/settings/cache wich size is determined by you and your SD card size ! (See screenshot!)
A simple fstab modification could work, however the script does do a lot of things beside copying everything to EXT. It also sets up some symlinks during every boot, so a part of the script is needed always. Also there is 2 EXT partitions, and the /data/data is stored on a 2nd EXT partition in an EXT4 loop file image So it's not that easy to simply mount it via fstab.
byr2

dkelley said:
Byr2.... just wanted to say this is first thing i read today and without coffee all I heard was
Blah blah blah dangerous blah blah blah faster blah blah risk blah blah even faster
Lmao
Click to expand...
Click to collapse
Hahaha. I've read this several times now and still all I get is what you wrote above.

I got this after all
Code:
$mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
none on /acct type cgroup (rw,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime)
/dev/block/mtdblock5 on /mnt/asec/mtddata type yaffs (rw,nosuid,nodev,relatime)
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
All correct?

This is mine:
Code:
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
none on /acct type cgroup (rw,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime)
/dev/block/mtdblock5 on /mnt/asec/mtddata type yaffs (rw,nosuid,nodev,relatime)
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_ut
ime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.qualcomm.qx.neocore-1 type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,fmask=0222,dmask=0222,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Seems your's almost the same...
The key is this:
Code:
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
How is your phone performing? Was everything OK?
byr2

Everything seems to be ok )
There is no more sticking when new apk installed. Quadrant score around 500.
I have Class 10 sd card (prooflink).
But I have had a little problem - not enough nand space to hold all of my apks, so I've decided to push most of them via adb from my laptop after Hero's reboot.
Quadrant score not so high as I expected, but anyway I'm happy =)

if you push it via ADB after reboot, than it should get to the right place
The quadrant score is affected by 3D and CPU also, but can you feel the "speed" while testing the IO? Does it run fast? How long is the DB read/write, FS read/write?
I'm happy someone else could get this thing working
byr2

[Q] Problem with installing apps to SD

Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.

kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.

kuba725 said:
Hi ,
My phone is kaiser i have froyo 2.2.2 and i install it to flash not with haret method. I install system to nand and data to sd partition but apps doesn't go to my sd card they are installing on internal memory (even they downloading to internal memory ). When i go to applications and click move to sd card then i see information that sd card is removed.
I changed many times to data to ext2 and other options but same think.
Any ideas???
I downloaded my ROM from sourceforge
Sorry for my bad english.
Click to expand...
Click to collapse
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.

daedric said:
Your rom probably has Terminal installed, if not download it from market.
After you have it, open it, and run " mount " without the quotes. Paste the result or screenshot.
Click to expand...
Click to collapse
I can't mount in terminal i have only this
$ export PATH =/data/local/bin:$PATH
$
SD card is in.
ohhh sory i must write mount .....

I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$

n2rjt said:
You have data to sd partition. I don't know if anyone has ever gotten that configuration to work with the option to move apps to SD, and I don't know any advantage in doing so.
If, on the other hand, you had data on NAND, you would want to be able to move apps to SD. I think scooter got that to work once, but I have never had success. I have tried many times. Something about the way we mount /sdcard versus /mnt/sdcard, I think, but not sure.
Click to expand...
Click to collapse
You say that i will be able to move apps to SD when data will be on Nand but i have this same issue that when i go to aplications and i click move to SD then i see information "SD card removed" (this information not always show up) then when i go to my apps i dont see this application . One time this have succes to transport it on sd and one time dont have succes

kuba725 said:
I have this in terminal :
$ export PATH=/data/local/bin: $PATH
$mount
rootfs on / type rootfs (rw)
proc on / proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcb1k0p1 on /sdcard type vfat (rw,noatime,nodiratime, fmask=0000, dmask=0000,allow_utime=0022,codepage=cp437 , iocharset=iso8859-1,shortname=nixed,utf8,flush,errors=remount-ro)
/dev/block/mtdblock2 on /system type yaffs2 (ro,nodev,relatime)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nodev,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
tmpfs on /sqlite_stmt_journalist type tmpfs (rw,relatime,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuct1 type cgroup (rw,relatime,cpu)
/dev/block/mtdblock2 on /bin/su type yaffs2 (ro,nodev,relatime)
$
Click to expand...
Click to collapse
Okay, now you are running with data on yaffs (which is NAND). Now you have the problem that all or most of us have. When I try to move an app to SD, it sometimes appears to work. Then, I reboot, and the app is gone.
Can we pool our knowledge and figure out how to make this feature work?

I like kaiser but he is was not created for android and i think that i will buy new phone , mayby SAMSUNG I5700 he have android 2.1 and 800 mhz is good and he has a lot of support from XDA

Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.

daedric said:
Kaiser was not made for android. But then again, no device was. Take the HD2, made for Winmobile 6.5 IIRC, is running W7, Android, and probably Maemo and Ubuntu and what not.
The problem with porting Android to kaiser is, first we don't have the support of google or a major provider, like HTC or Motorola.
Second, we're working blind here, we're trying to guess or find/hack many things...
Still, to take a device Announced in July 2007, with 128mb RAM, 256 rom, MSM7200 400Mhz with a Adreno 130 GPU and make it work with android, it's a damn good achievement.
Don't be sad it doesn't work oh so well, be glad it works better than windows mobile.
Click to expand...
Click to collapse
I don't think that kaiser is bad phone is very good but i need some new stuff
I don't have too much money, for me HD2 is best phone ever but is too expensive.
Hmmm Maybe you know some cheap phone better than the Samsung I5700???

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

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 ?

Access to /storage/sdcard0 requires root access

Something strange appeared at my SM-605.
I cannot access /storage/sdcard0 without root any more.
Total Commander shows "Insufficient Memory : rootfs lost on reboot" and mounts this partition every time using mount -o remount,rw -t rootfs rootfs /
The same is for /storage/emulated/legacy and /mnt/sdcard
At the same time accessing using /mnt/shell/emulated/0 works just fine.
Re-creating links in /storage does not help.
/etc/vold.fstab never was modified.
What is going on and how to fix it?