Database Info

[Q] how to tell android to detect my sd card storage as external storage

Hello xda hackers,first off I'd like to say this is my first post here but your forums (and forum members work) has helped a lot.
I've recently been experimenting with xfs for my "sd card" on my nexus s.
(just to see the performance difference between xfs,fat32 and ext4 on my nexus s)
I've successfully compiled mkfs.xfs for arm and I’ve successfully formatted my sdcard storage with xfs. I’ve even gotten it to mount fine in android (btw, i use a custom kernel based on netarchy's git repo). i can verify it's mounted(i've even gotten it to mount at boot because vold.fstab just wasn't working). and i can even access files on it using some file browser apps.
the problem I'm having is that all of my apps think i don't have "external storage".
I've even done setprop EXTERNAL_STORAGE_STATE mounted
camera,music,etc.... all the apps say i don't have usb/external storage.
so i just wanted your help in finding out how exactly android tells if a mount-point is external storage or not.
FYI: my nexus s doesn't really have an sd card it's an internal storage (i think nand).
here is the output of some commands in case you need it:
adb shell mount:
Code:
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw,noatime,barrier=0,nobh,data=ordered 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=0,nobh,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p3 /mnt/sdcard xfs rw,noatime,attr2,noquota 0 0
none /sys/kernel/debug debugfs rw,noatime 0 0
adb echo $EXTERNAL STORAGE :
# echo $EXTERNAL_STORAGE
/mnt/sdcard
feel free to ask me for more info. and yes I’ve googled it all over and plenty of people have tried helping me on irc. all the topics that come up is about people having their sd cards not detected.

mkfs.xfs in case anyone wants it.
oh, and I’ve attached mkfs.xfs for those of you who want to run it from your phones but don't want to compile it from the source(it took me a few hours to get around some of the compilation/cross-compilation issues).
it's 1.8Mb because it's statically linked.

nvm, i got is solved by hacking around vold. thanks for all the help...Not.

i cant mount sdcard storage
hi i have samsung galaxy 3 i5800
end i instaled on my phone kyrilos v9.4 rom
end now i want to mount sdard storage bat wen i go to the recovery
i choice mount sdcard storage,mount sdcard ext end reboot nothing hapen
i go back to recovery end i have agen option mount sdcard that mean my card is not mounted
pleace i need som healp this is my first android phone
sory for my english

[Q]Prestigio PMP5080C PRO - Rooting

Hey everyone, I'm new to the forum, and am in need of great help
A few days ago, I bought a new tablet, the Prestigio PMP5080C Pro. It's actually a very good tablet for the price you're paying. I've only had 2 problems:
1)They don't have any settings to enable proxy (Can't connect to internet at campus).
2)Many of the 3D games show only white textures (Apparently Chainfire 3D fixes this issue).
Now to fix both of them, I need root access. And that's the biggest problem I've been having.
The device uses Android ICS (4.0.3). At first I had many problems trying to get the device recognised as anything other than a USB Mass Storage Device, but eventually got it working. After that, I tried using SuperOneClick 2.3.3, it got past step 2, but then froze on step 7. No matter what I tried, it froze there everytime. After that, I tried using UnlockRoot, and it just showed the steps (completed in like 15 seconds) and didn't give me any completed messages. After that failed, I tried using RootThat, and got this log:
Code:
adbd cannot run as root in production builds
List of devices attached
ASBSM805HCZ01234 device
adbd cannot run as root in production builds
remount failed: Operation not permitted
failed to copy 'C:\RootThat\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'C:\RootThat\Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
::Success!!::
After that failed, I read up about using Wendal's RK29xxImageTools_v2.1 to unpack and repack the firmware with superuser access. It managed to unpack the firmware file (Can see the system.img, etc) but when it tries to add the root, it gives the following error towards the end:
Code:
cramfsck: superblock magic not found
Enable root permission
The system cannot find the path specified.
The system cannot find the path specified.
chmod: cannot access `system/*': No such file or directory
chmod: cannot access `system/bin/su': No such file or directory
chmod: cannot access `system/app/Superuser.apk': No such file or directory
Unpack -- All Done
Pls input: 1-Unpack 2-Pack 3-Exit
Okay, so my first question. How do I know what filesystem /system is using? I typed in "mount" in adb shell, and I get the following:
Code:
C:\Users\Xenonification>adb shell
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
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/mtdblock8 /system ext3 ro,noatime,nodiratime,barrier=0,data=ordered 0
0
/dev/block/mtdblock6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=contin
ue,barrier=0,data=ordered 0 0
/dev/block/mtdblock5 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=conti
nue,barrier=0,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch****t=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relati
me,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,ioch****t=iso8859-1,sh
ortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/org.vudroid-1 vfat ro,dirsync,nosuid,nodev,relatime,ui
d=1000,fmask=0222,dmask=0222,codepage=cp437,ioch****t=iso8859-1,shortname=mixed,
utf8,errors=remount-ro 0 0
[email protected]:/ $ mount
C:\Users\Xenonification>
"/dev/block/mtdblock8 /system ext3 ro,noatime,nodiratime,barrier=0,data=ordered 0 0" Does that mean it's using the ext3? Because elsewhere I've heard that it uses cramfs, so i'm not sure
And secondly, does anyone know any other methods to root this device? I was thinking about mounting the system.img, adding the files needed for root, and then repacking the firmware. But I have no idea how to do this.
Thanks guys!

Rooted roms there: http://forum.xda-developers.com/showthread.php?t=1796067
yes it's using ext3 mount output is "device mountpoint filesystem options", you can mount it in any standard (or user-friendly if you want) linux distribution by "mount image mountpoint -o loop" as root
Btw I've tried chainfire and device didn't boot, it's very probable I did something wrong but do chainfire support opengl1.1-only devices?

[Q] Wiped /cache now unable to access /sdcard

I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
In adb I tried to cd into /sdcard and the directory is missing entirely
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
same thing here
Code:
[email protected]:/ $ cd /storage/emulated/legacy
/system/bin/sh: cd: /storage/emulated/legacy: No such file or directory
My mountpoinits show no sign of sdcard anywhere
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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstunts-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.tribok.android.livewallpaper.nightflare.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.robbers.clock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
If anyone has any suggestions I would appreciate them. I would really like to be able to recover my data from the device before I wipe it.

Alias.TDP said:
I screwed up a bit here. I was using the stock recovery to format my /cache partition but about 5 minutes in it froze. Figuring that something had went wrong i hard rebooted the phone and now when I boot it appears that my internal sdcard partition has disappeared.
.
Click to expand...
Click to collapse
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)

GUGUITOMTG4 said:
Here you go, just flash cache.img on this thread (method 2)
http://forum.xda-developers.com/showthread.php?t=2513701
Your data may be lost at all so, if it does not work, then use flash-all method (method 1)
Click to expand...
Click to collapse
Thanks dude that worked

Alias.TDP said:
Thanks dude that worked
Click to expand...
Click to collapse
Glad it's fixed. Keep that thread in the first aid kit:cyclops:

Remember - NEVER reboot your phone when it's trying to wipe. Some of these phones take an exceptionally long time to wipe depending on your recovery.

Q/A/Discussion CyanogenMod 11 - Android 4.4 [FXP]

Message from Moderator: All Discussion/Question/Answer related to CM 11 goes in this thread.
Hello,
Me and maybe many more people can not post in the dev thread so i post my question here.
I can not see the files of my internal memory in PC. even after i execute
mount -t vfat -o nosuid,nodev,noexec /dev/block/vold/259:0 /storage/sdcard0
Click to expand...
Click to collapse
in a ssh session with root user i can not see my files
Anybody with the same problem?
any workaround
By the way may thanks to varun for his hard work, finaly we have a decent rom for our phones!!

Update: even after I enter in ftp I can not see files in /sdcard0

so am i, i can't get root acces in internal storage using cm file explorer

Hi, has anybody problem with GPS? My doesn't work in any apps

When I boot and enter in ssh I see
[email protected]:/data/data/berserker.android.apps.sshdroid/home # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.doubleTwist.androidPlayerProKey-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobisystems.editor.office_registered-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.jrtstudio.iSyncr-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.melodis.midomiMusicIdentifier-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/rg.adrengton.lighting-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.nynix.knots3d-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-6 /mnt/asec/tillekesoft.AndroidDreamer-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-7 /mnt/asec/com.xtrend.nxtrend-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-8 /mnt/asec/com.aldiko.android-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-9 /mnt/asec/com.vuplus.vuplusplayer-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-10 /mnt/asec/com.linxmap.androidterminal-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-11 /mnt/asec/com.realvnc.viewer.android-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-12 /mnt/asec/info.lamatricexiste.network-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/ftmd /ftmd ext4 rw,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/ftma /ftma ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat 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
/dev/block/vold/259:0 /mnt/media_rw/sdcard0 vfat 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/block/vold/259:0 /mnt/secure/asec vfat 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/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=2800,group_id=2800,default_permissions,allow_other 0 0
Click to expand...
Click to collapse
that should not be mounted at /storage/sdcard0 right?
if i go to /storage/sdcard0 and do a "ls" it responds me
[email protected]:/storage/sdcard0 # ls
ls: can't open '.': Permission denied
Click to expand...
Click to collapse
In ftp
500 Couldn't list directory. Check config and mount status.
: /storage/sdcard0//storage/sdcard0
Click to expand...
Click to collapse

Flash the file attached here. after flashing varun's camera fix
It makes your phone run the mount command automatically after every reboot, with a small delay, so vold doesn't break it again.
EDIT:
Or use freakzapster's Camera_fix+storageworkaround ZIP file from http://forum.xda-developers.com/showpost.php?p=52294221&postcount=102

Cameras
Cameras working :
Camera FV-5
Camera Zoom
DSLR Camera
Cameras Not Workin:
Google Camera
HdrCamera
Instagram

StillBrilliant said:
Flash the file attached here. after flashing varun's camera fix
It makes your phone run the mount command automatically after every reboot, with a small delay, so vold doesn't break it again.
EDIT:
Or use freakzapster's Camera_fix+storageworkaround ZIP file from http://forum.xda-developers.com/showpost.php?p=52294221&postcount=102
Click to expand...
Click to collapse
thanks.
With this file my phone mounts the internal SDcard and i can acess it from ssh and ftp but i can not delete files and from pc Internal storage does not apear (previosly I could see it but not the files in it)
regards

First: thanks for the great effort. CM11 is a godsend.
I'm having trouble with the storage, tho.
Evernote can't write het database
SwiftKey can't download language packs
Export from dropbox fails
Bluetooth filetransfer fails
File download in browser fails with a FC
I have flashed the zip with the fix, the storage gets mounted properly. But it seems not all apps know how to handle it.
Can it be a problem that is flashed over an older Cm version? Should I first have flashed to stock?
Almost there

For me looks like now it's working, including camera
I had to reinstall Jelly Bean ftf from sony> gain root acccess > install kernel with recovery > install varun CM11 > Gapps > reboot > install StorageWorkaround.zip > install Camera_fix.zip
Now all seems to work and I can access files from diferent sources .
Maybe it was because I install varun CM11 over Mr.Stenly CM11
regards

Look into this one..
while installing zip, I am getting this kind of error:
symlink : some symlink error
and installation gets aborted.
And when I try to reboot using CWM, the phone gets stuck on bootloop. Please help! thanks

Be careful with Internal Storage
After some strugle I can access it but I copied some files to it and instaling Apps from it failed with " an error occured analyzing the package" and I also could not copy my old fotos to respective folder in Internal

unwantedidiot said:
while installing zip, I am getting this kind of error:
symlink : some symlink error
and installation gets aborted.
And when I try to reboot using CWM, the phone gets stuck on bootloop. Please help! thanks
Click to expand...
Click to collapse
yA am also getting the same problem.can someone help us plz

jokerpappu said:
yA am also getting the same problem.can someone help us plz
Click to expand...
Click to collapse
okay here's a way
Extract the boot.img from the CM11 zip
Flash the boot.img using Flashtool or adb
Boot into recovery and Flash CM11
Cheers~

Me_Shazzy said:
okay here's a way
Extract the boot.img from the CM11 zip
Flash the boot.img using Flashtool or adb
Boot into recovery and Flash CM11
Cheers~
Click to expand...
Click to collapse
what about the gapps not being flashed???

StillBrilliant said:
Flash the file attached here. after flashing varun's camera fix
It makes your phone run the mount command automatically after every reboot, with a small delay, so vold doesn't break it again.
EDIT:
Or use freakzapster's Camera_fix+storageworkaround ZIP file from http://forum.xda-developers.com/showpost.php?p=52294221&postcount=102
Click to expand...
Click to collapse
thanks a lot man now it is perfect

network
manual celular network search not working For me :/

Me_Shazzy said:
okay here's a way
Extract the boot.img from the CM11 zip
Flash the boot.img using Flashtool or adb
Boot into recovery and Flash CM11
Cheers~
Click to expand...
Click to collapse
Hey, it worked..thanks a lot

i tried to write the command in terminal emulator,but it said device or resource is busy,what's wrong? :crying:

indroiders said:
i tried to write the command in terminal emulator,but it said device or resource is busy,what's wrong? :crying:
Click to expand...
Click to collapse
Did you flash Varun's camera fix first?
PS. Even I got the same error, but then I checked, I could access my files from galleries, file explorer. Try it.

How to verify 'discard' flag working in fstab.cardhu?

I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?

gc2712 said:
I have TF700 running Crombi-KK F2FS on data, and added the 'discard' flag to fstab.cardhu to (hopefully) ensure trim of flash memory. Is there some way to verify that the discard function is working?
Click to expand...
Click to collapse
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device

sbdags said:
The fstab,cardhu gets modified by my boot process depending upon what you chose. I intentionally remove the discard option as it cause me bootloops.
However to check if yours has persistd ( and it may have if you haven't been anywhere near data2sd or rom2sd) is run the following in a terminal
mount | grep /dev/block/*
look for the /data and you will see what options it has been mounted with, interested to see if discard has persisted and why it won't work on my device
Click to expand...
Click to collapse
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?

gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go

sbdags said:
You can't edit the fstab directly as it gets replaced by the kernel on every boot.
so go to /system/boot/print.d
Open 30fstab-f2fs in a text editor
On this line change it from
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime,//;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
to
$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu
Reboot but be prepared for a bootloop that you can only fix by undoing what you just did.... Have a nandroid ready to go
Click to expand...
Click to collapse
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.

gc2712 said:
Just a cautious check on syntax before I do this. Every other flag on that line is of the form: ;s/flagx,// , yet in this instance you suggest just forward slash after 'nodiratime', ending with just a forward slash instead of two forward slashes. Is this intentional or should the syntax be: //;s/nodiratime,//;s/discard,//;s/noauto_da_alloc, etc.
Although I've used linux for years (Since Red Hat 7!) and have just enough knowledge to follow instructions to edit scripts, I still don't grasp syntax very well. (Just enough to know if I get it wrong things screw up
Also, if I save a copy of the 30fstab-f2fs file to sdcard can I simply copy it back using TWRP (latest) instead of a full nandroid restore?
Sorry if these are dumb questions. Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.

sbdags said:
Yes it is my correct - my edit will replace nodiratime with discard Your edit will look for discard (which isn't there) and replace it with nothing
Personally I'd do a full nandroid but yes as long as you can partially recover then that single file should be ok.
Click to expand...
Click to collapse
Many thanks (red face here). I'll give it a try today and do the full nandroid backup just in case. Will report back the result.

Well! That was a debacle.:crying:
Changed to:
"$BB sed -i '/mmcblk0p8/{;s/ext4/f2fs/;s/barrier=.,//;s/nodiratime/discard/;s/noauto_da_alloc,//;s/nomblk_io_submit,//;}' /fstab.cardhu "
It didn't boot loop, but eventually booted into a screen which said, "Encryption Unsuccesful. Encryption was interrupted and can't complete. As a result your tablet is no longer accessible" etc....
Thank god for the nandroid! When I reflashed the nandroid, TWRP reported that it was formatting system to ext4 even though it was originally F2FS. However when I rebooted and checked in terminal it indicated that the FS on system was in fact F2FS.
# mount |grep /dev/block/mmcblk0p8
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
No idea why, but its all working again, but alas, no 'discard' option. Could this be the reason?
[email protected]:/ # fstrim -v /data
fstrim: FITRIM: Inappropriate ioctl for device
Don't know what that error means and google wasn't my friend this time.

gc2712 said:
I tried running the above command in terminal. Without su just got 'permssion denied' on all. With su there was no response in terminal at all So just tried:
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc 0 0
/dev/block/mmcblk0p8 /data f2fs rw,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.chrome_cache /data/data/com.android.chrome/cache tmpfs rw,relatime,size=102400k 0 0
mobi.mgeek.TunnyBrowser_cache /data/data/mobi.mgeek.TunnyBrowser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Looks like the discard flag was just ignored? Any way to make it persist?
Click to expand...
Click to collapse
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...

LetMeKnow said:
Here is my /dev/block* information:
Code:
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
sysfs /sys sysfs 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,noatime,nodiratime,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0
[COLOR="RoyalBlue"]/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,noauto_da_alloc,discard 0 0[/COLOR]
[COLOR="RoyalBlue"]/dev/block/mmcblk1p2 /data f2fs rw,noatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0[/COLOR]
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
browser_cache /data/data/com.android.browser/cache tmpfs rw,relatime,size=102400k 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /Removable/MicroSD texfat rw,relatime,uid=1000,gid=1015,umask=0000,
allow_utime=0022,nls=utf8,min_prealloc_size=64k,readahead=4M,discard,errors=continue 0 0
[email protected]:/ #
It seems to stick with the "discard" mounting flag...
Click to expand...
Click to collapse
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?

gc2712 said:
What is the additional partition mmcblk1p2 for data? The partition mmcblk0p8 which on my system is my data partition has been located on /datai and is ext4 on yours. How does that happen? Are you using data2sd or something?
Click to expand...
Click to collapse
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.

LetMeKnow said:
Yes, you are correct. I am using Data2sd. I am running f2fs on my external data partition (/dev/block/mmcblk1p2) and leave my internal data partition as ext4 because it is just a backup data partition that I actually never use it.
Click to expand...
Click to collapse
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.

gc2712 said:
Ah! Mystery solved then. sbdags was right then that with internal F2FS /data the discard option will bootloop, or, as in my case boot and trash the data partition requiring factory reset. Hopefully, the F2FS file system and KitKat manage garbage collection well enough without fstrim/discard as I don't want to reinstall again as ext4 at this point. Perhaps someone will make it work in the future.
Click to expand...
Click to collapse
Hmm, I did help one user using f2fs on internal data partition with discard flag on JB Rom. He had no issue until moving on with KK Rom. If I can have the tf700 long enough, I will test it out on the internal data so we can rule it out...
Garbage collection is to reclaim your locked up or old memory that old apps keeps holding on without using them. I believe that is what it is for but I may be wrong...