Related
Helo,
How do I take full NAND dump of Android phone for forensic analysis ?
Is there is any utility for it ?
Sorry I am new in this field.
trying to spy on your girl friend?
TRusselo said:
trying to spy on your girl friend?
Click to expand...
Click to collapse
no!
I just want it for education purpose.
Have you found an answer?
rakesh.sharnagate said:
Helo,
How do I take full NAND dump of Android phone for forensic analysis ?
Is there is any utility for it ?
Sorry I am new in this field.
Click to expand...
Click to collapse
What you need first it ROOT. After you have root, read on.
Put a blank micro SD card into the device (at least 2GB or more is recommended)(there are other methods, but this one is simpler to explain).
Get yourself into an ADB shell, and run the following command:
Code:
mount
That should give you something like this:
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
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,nodelalloc,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=mixed,errors=remount-ro 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/dm-0 /mnt/asec/com.iplod-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.studio215.bigbangwhip-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.acrossair.tvguideuk-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.dancingpixelstudios.sixaxiscontroller-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
Find where your what dev is mounted as your /data partition. In this case it is /dev/block/platform/msm_sdcc.1/by-name/userdata. Other devices may have different names.
Know where your mSD card is mounted, let's say /sdcard/external_sd/.
Drop to root if not already root, the following commands will be with "#" prefix.
Image the data partition:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/sdcard/external_sd/data.dd
dd = disc dump
if = input file
of = output file
Dumping the image should take a while, perhaps 5-20 minutes, depending on device.
You should have a raw image of your /data partition for forensic analysis.
Hi, sorry if it is the wrong forums, I'm looking for help in order to swap memory in Tablet 7" Icoo D70PROII, the Tablet is rooted and I'm trying to use the "External 2 Internal" App, but I've a doubt about one of the paremeters that must be configured (Custom Settings) becuars the device is not listed.
Below are details about devices and one posible configuration, I'm wondering someone could check it (without any compromise or responsibility !) and tell me if can be correct.:
The original internal mounting point
/mnt/sdcard
The original external mounting point
/mnt/external_sd
The ext. sdcard device access
/dev/block/vold/179:1
That would be ok.. ?? DEvices lists:
Hi, 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 ext4 ro,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /mnt/asec/com.antutu.powersaver-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/eu.chainfire.supersu-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.ayelectronics.AppFolder-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=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-3 /mnt/asec/com.outfit7.talkingnewsfree-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Table 7” Icoo D70PROII
Model:rk30sdk
Firmware version:4.1.1
Status:ROOTED
Resolution:1024*600
Manufacturer:Icoo
Android Version:4.1.1
Kernel version:rk30sdk-eng 4.1.1 JRO03H 20121220.140255 release-keys
Thanks a lot in advance
Hej everyone!
I have a strange problem mounting my encrypted internal SD card. Most of the time it just doesn't work after upgraing to CM 10.2 nightlies.
When looking at the table of mounted storage devices I should get this (and a couple of /dev/block/dm-x nodes):
Code:
rootfs / rootfs ro,seclabel,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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/dev/block/mtdblock4 /cache yaffs2 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,seclabel,nosuid,nodev,noatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/vold/254:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
What I get instead is all the above but neither the "/dev/block/vold/254:1" nor the "tmpfs /storage/sdcard0/" line. Also all "/dev/block/dm-x" lines, except the dm-0 line are not there.
What I have found so far is that it seems as if I have to hurry do decrypt the sd card when I boot the phone to get my sd mounted and if it fails to mount then under /dev/block I get a dm-0 device node, but no dm-1.The /dev/block/vold/254:1 node is also missing when mounting fails. This makes me think the devices are not found and thus not created at boot time.
When my sd card is mounted I also have no problem using it.
Has anyone any idea?
chnage it to MTP
leap_ahead said:
chnage it to MTP
Click to expand...
Click to collapse
Thanks, but this didn't work. My Nexus is always automatically switching back to mass storage. Also I am not sure why this would help. The SD card isn't even recognized by the phone, so how could my PC?
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...
Hi everybody,
I'm trying to port a 4.4.4 rom for HTC Sensation xl wich only have an internal sdcard. The rom boot but the internal sdcard is not mounted , whatever rom i use as base. When I use a 4.4.2 rom as base, i can't acces the internal storage cause it said that the folder is missing or doesn't exist. When I use a 4.4.4 rom as base, it said that i "need more permission" and the internal storage file is empty even if i can see all the files in it from recovery.
I've try these solutions to fix the problem but none of them worked :
1) Put the base storage file in port framework-res.apk
2) Put the base vold.fstad file in system/ect/ folder
3) Take the sdcard file from base bin folder to port bin folder
when I try to see what is mounted in terminal emulator, this is what i get :
[email protected]:/ $ su
[email protected]:/ # 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
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/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0h
/dev/block/mmcblk0p30 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p32 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
[email protected]:/ #
But when i compare it with what i get from a rom with sdcard mounted, i can see that there's three lines missing at the end and these lines are about the sdcard
[email protected]:/ $ su
[email protected]:/ # 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
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/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p30 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p32 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:34 /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/179:34 /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=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
From a file manager i see that the 179:34 and fuse files are present in the rom wich doesn't mount the sdcard but i can't understand why the internal storage is missing.
For now, i really don't know how to fix the problem and i need your help.