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] Is it possible to resize the internal partitions on the Play?

Apologies if this has already been asked elsewhere, but I got no search results on it...
I was checking partition sizes using Root Explorer yesterday, and the following is what I was seeing:
Data: 380MB, 65.11MB free
System: 312.5MB, 83.02MB free
Cache: 225MB, 1.31MB used
This works out at around 1GB of internal storage, and on my phone, over 300MB wasted between system and cache partitions. Is the large cache partition there for downloading all that extra game data, because it seems needlessly large otherwise?
The big question though - is there any way to repartition the internal storage?

Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk

AndroHero said:
Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...

drunkenfcuk said:
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...
Click to expand...
Click to collapse
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en

AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
maybe they added it into an ext recovery, so maybe we could use CWM with 2.3.4?

AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
Thanks, I'll take a look
Do you have 2.3.4? You can use ADB to list the partitions, so you might be able to see where that 100MB has gone...
adb shell
df -h
I get the following:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 199.0M 76.0K 198.9M 0% /dev
tmpfs 199.0M 0 199.0M 0% /mnt/asec
tmpfs 199.0M 0 199.0M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 190.8M 121.7M 61% /system
/dev/block/mtdblock3 380.0M 296.4M 83.6M 78% /data
/dev/block/mtdblock2 225.0M 1.3M 223.7M 1% /cache
/dev/block/mtdblock1 10.0M 1.5M 8.5M 15% /data/idd
Or just 'df -h' from a terminal window on your phone...

Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here

Azeazezar said:
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here
Click to expand...
Click to collapse
I suppose if it's hidden from Android, then ADB wouldn't see it anyway. And it's actually more than 100MB. More like 123.5MB. Would love to know where it's gone!

Symlinks on 101 G9

i tried to make a symlink on my archos but when i tried it gave Function not implemented.
is there a way to implement this function?
Gr.Roymar

roymar said:
i tried to make a symlink on my archos but when i tried it gave Function not implemented.
is there a way to implement this function?
Gr.Roymar
Click to expand...
Click to collapse
Hi
Where are you trying to create these symlinks?
On the A101S you cannot create symlinks in /mnt/sdcard because this is a vfat partition which does not a support symlinking, you also won't be able to make link in /mnt/storage ; /mnt/data ; /storage ; /sdcard ; This is because these are mounted by the sdcard service which is designed to provide a windows friendly fat view onto the file system.
Creating links anywhere else shouldn't be a problem ( depending on the filesystems you are using )
Hope tjhat helps.

trevd said:
Hi
Where are you trying to create these symlinks?
On the A101S you cannot create symlinks in /mnt/sdcard because this is a vfat partition which does not a support symlinking, you also won't be able to make link in /mnt/storage ; /mnt/data ; /storage ; /sdcard ; This is because these are mounted by the sdcard service which is designed to provide a windows friendly fat view onto the file system.
Creating links anywhere else shouldn't be a problem ( depending on the filesystems you are using )
Hope tjhat helps.
Click to expand...
Click to collapse
Thanx for you're answer.
i was indeed trying to make a symlink in /storage because of de maps of the sygic navigator take a lot of room
Greetz Roymar

roymar said:
Thanx for you're answer.
i was indeed trying to make a symlink in /storage because of de maps of the sygic navigator take a lot of room
Greetz Roymar
Click to expand...
Click to collapse
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers

trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect on "symlinked" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
That's a great solution, thank you for the effort
a thanx for you

trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
I have archos G9 101 Turbo 250GB HDD
i try with this solution but cant true
app install to internal memory

acasilver said:
I have archos G9 101 Turbo 250GB HDD
i try with this solution but cant true
app install to internal memory
Click to expand...
Click to collapse
I would expect that to be case, This apply's to the SD Versions only, It should be fairly trivial however to change the new location to an hard disk partition. Can run the following adb command and post the output here, then i'll see if I can point you in the right direction :good:
Code:
adb shell mount
Thanks

trevd said:
I would expect that to be case, This apply's to the SD Versions only, It should be fairly trivial however to change the new location to an hard disk partition. Can run the following adb command and post the output here, then i'll see if I can point you in the right direction :good:
Code:
adb shell mount
Thanks
Click to expand...
Click to collapse
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Enable_SDE>adb shell mount
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=455588k,nr_inodes=113897,mode=755 0 0
/dev/mmcblk0p2 /mnt/system ext4 rw,noexec,noatime,user_xattr,barrier=1,data=orde
red 0 0
/dev/loop0 / squashfs 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
usbfs /proc/bus/usb usbfs rw,relatime,devuid=1000,busuid=1000,listuid=1000 0 0
tmpfs /tmp tmpfs rw,relatime,mode=775,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,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/mmcblk0p1 /mnt/rawfs rawfs rw,relatime 0 0
/dev/block/mmcblk0p2 /mnt/system ext4 rw,nosuid,noexec,noatime,user_xattr,barrie
r=1,data=ordered 0 0
/dev/block/mmcblk0p4 /data ext4 rw,nosuid,noatime,user_xattr,barrier=1,data=orde
red,noauto_da_alloc 0 0
/dev/fuse /mnt/nand fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1015,def
ault_permissions,allow_other 0 0
/dev/block/vold/8:1 /mnt/storage ext4 rw,nosuid,nodev,noexec,noatime,nodiratime,
fmode=0664,dmode=0775,uid=1000,gid=1015,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/8:1 /mnt/secure/asec ext4 rw,nosuid,nodev,noexec,noatime,nodirat
ime,fmode=0664,dmode=0775,uid=1000,gid=1015,user_xattr,barrier=1,data=ordered 0
0
tmpfs /mnt/storage/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
C:\Enable_SDE>

doesn't work on CM10.1
Hello,
Thank you for your methods!
I used your method 2 on Blue ROM (4.0.4) with success but I just put the CyanogenMod 10.1 and it doesn't work anymore, here is the command line I put on my script for CM10.1 :
mount -o bind /storage/sdcard1/Android /sdcard/Android
It only works on ADB command from the PC, if I try on Terminal emulator on the tablet I have no error but no effect.
Do you have a solution please?

pourmadeesse said:
Hello,
Thank you for your methods!
I used your method 2 on Blue ROM (4.0.4) with success but I just put the CyanogenMod 10.1 and it doesn't work anymore, here is the command line I put on my script for CM10.1 :
mount -o bind /storage/sdcard1/Android /sdcard/Android
It only works on ADB command from the PC, if I try on Terminal emulator on the tablet I have no error but no effect.
Do you have a solution please?
Click to expand...
Click to collapse
Yeah that sounds about right, it's because the /storage directory on 4.2.2 ( CM 10.1 ) is just a "virtual directory" the real data is /data/media/0 try changing your bind to there, You can probably just get away with a symlink especially if you're external sdcard is in ext4... I'll have to have a play with that!! :good:

Thank you, it works from Terminal Emulator!
An another linked question :
I restored my Gameloft games (Ice Age Village, MIB,... and Rayman) from Titanium Backup as usually but this time I have problem once I put this symlinks, it tells me I need to download datas I select Yes or ok but I have an error and I can't play, I precise it's only with CM10.1 with symlinks, I did it many time with 4.0.4 with no problem

pourmadeesse said:
Thank you, it works from Terminal Emulator!
An another linked question :
I restored my Gameloft games (Ice Age Village, MIB,... and Rayman) from Titanium Backup as usually but this time I have problem once I put this symlinks, it tells me I need to download datas I select Yes or ok but I have an error and I can't play, I precise it's only with CM10.1 with symlinks, I did it many time with 4.0.4 with no problem
Click to expand...
Click to collapse
Hmm, Maybe the Symlink method is no good for you in this particular instance. Just to be clear are you saying you used "mount --bind" or did you go with a symlink using the "ln -s" command... At a wild guess I'd be inclined to thing it maybe be some anti-piracy measure in Gamesloft Games or it could be a permissions issue.
Just a little tip for you. If you're going to ask questions you're going have to bring folks more than "I've got an error" That's doesn't tell anyone anything really.... What does the error say? for starters. The more info you have the better. Then the people who want to help can help and you get to play you're games a whole lot sooner :good: Winners All round :silly:

trevd said:
Hmm, Maybe the Symlink method is no good for you in this particular instance. Just to be clear are you saying you used "mount --bind" or did you go with a symlink using the "ln -s" command... At a wild guess I'd be inclined to thing it maybe be some anti-piracy measure in Gamesloft Games or it could be a permissions issue.
Click to expand...
Click to collapse
I did this command :
Code:
mount -o bind /storage/sdcard1 /data/media/0
My goal is to get "data" and "obb" at least on the sdcard instead of internal memory, am I doing the right thing?
Just a little tip for you. If you're going to ask questions you're going have to bring folks more than "I've got an error" That's doesn't tell anyone anything really.... What does the error say? for starters. The more info you have the better. Then the people who want to help can help and you get to play you're games a whole lot sooner :good: Winners All round :silly:
Click to expand...
Click to collapse
You're allright, here is some two screenshot of MIB without symlinks :
If first ask for additionnal files, I select Yes and it starts downloading.
But, if I run the mount command, after the first screenshot asking additionnal datas, I get this message (and screenshot doesn't work, "Couldn't capture screenshot. Couldn'tsave screenshot. Storage may be in use.") : "A problem occured and the download could not be completed successfully. Do you want to restart the download? An unstable network may cause problems when downloading." I select Yes but additionnal datas message and the same message bootloop. It seems it's a storage problem...
For Rayman, it starts without problem without symlink and I get a "Download error, please make sure you are connected to Internet and try again later" with mount command. Of course I'm connected...
Hope you can help me

Nobody knows what is the problem with symlinks and CM10.1 ?

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

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 ?