Related
I'm trying to debug why /data won't mount. Can someone post the output of there mount command?
Here is my output and sure enough /data is not mounted:
/ # mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl10 /system ext4 rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=writeback,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl7 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
However if I do a ls on / I see /data and it does have files there:
drwxrwx--x system system 2004-12-31 16:10 preinstall
dr-x------ root root 2004-12-31 16:10 config
drwxrwx--x radio radio 2004-12-31 16:10 efs
lrwxrwxrwx root root 2004-12-31 16:10 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2004-12-31 16:10 acct
drwxrwxr-x root system 2004-12-31 16:10 mnt
lrwxrwxrwx root root 2004-12-31 16:10 d -> /sys/kernel/debug
lrwxrwxrwx root root 2004-12-31 16:10 etc -> /system/etc
drwxrwx--x system system 2004-12-31 16:10 dbdata
drwxrwx--- system cache 2011-07-08 21:51 cache
lrwxrwxrwx system system 2011-06-15 19:34 bin -> voodoo/root/bin
drwxr-xr-x system system 2004-12-31 16:10 voodoo
-rwxr-xr-x root system 704 2011-05-31 07:28 lpm.rc
drwxr-xr-x root system 2011-06-15 19:34 lib
lrwxrwxrwx system system 2011-06-15 19:34 init -> voodoo/scripts/init_runner.sh
-rwxr-xr-x root system 10322 2011-06-15 19:32 recovery.rc
drwxr-xr-x root root 2011-07-07 23:51 system
drwxr-xr-x root root 2011-07-08 04:52 dev
dr-xr-xr-x root root 1969-12-31 16:00 proc
drwxr-xr-x root root 1969-12-31 16:00 sys
lrwxrwxrwx system system 2011-06-15 19:34 usr -> voodoo/root/usr
drwxr-xr-x root system 2004-12-31 16:10 sbin
-rwxr-xr-x system system 1613 2011-05-31 06:56 init.goldfish.rc
-rwxr-xr-x root system 118 2011-05-31 06:50 default.prop
-rwxr-xr-x root system 21663 2004-12-31 16:10 init.rc
drwxr-xr-x root system 2011-06-15 19:33 res
-rwxr-xr-x system system 141364 2011-06-15 19:32 init_samsung
-rwxr-xr-x root system 351 2011-05-31 07:27 init.smdkc110.rc
-rwxr-xr-x root system 2737 2011-05-31 06:54 fota.rc
drwxrwx--x system system 2011-07-08 04:52 data
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl10 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl7 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
...Hope this helps your debugging
-On EE4 Vanilla Twist using PBJtime Kernel
Thanks for the quick response!
What rom are you running on? There are serious mounting/adb issues with the latest gingerbread leak
Do you happen to know the equivelent of /etc/fstab in android linux? I know a tiny bit about linux, but not anything android specific.
have been trying various mount commands with no success. I think the problem is that there is already a directory called /data that has data in it (presumably part of the rootfs) when really it should be mounted to /dev/block/mmcblk0p1. I'm hoping an ODIN flash will fix me up.
i have a boot.img with a size of 13mb, when i unpack it , it produce two files the boot.im-kernel and boot.img-ramdisk.cpio.gz,and it became much less in size, together they where 5.3mb and when i repack it using mkbootimg and flash it it wont flash. .
what i do to repack is , on the folder containing the ramdisk and kernel and the mkbootimg ' i typed mkbootimg --kernel "the kernel" --ramdisk "the disk" -o boot.img . .then i got an output boot.img
now when i flash it using fastboot
i type fastboot device.. then it shows my device.. and then i typed fastboot boot 'the boot.img i repack after i unpack'
then its says it been copied and rebooting. .but the device is still in downloading mode. .so i try again typed fastboot boot 'the boot.img' and now it says fastboot waiting for device. .so i think it was disconnected
now again i repack the kernel and ramdisk but with different command
i typed mkbootimg --kernel 'kerne' --ramdisk 'ramdisk' and i include other commands like --base --cmdline then -o boot.img
then i get the results boot.img again the flash it using fastboot
but this time it vibrates and turn off but didnt light up and in computer it mounts different partitions like sd mode
now they say there is a specific procedure of compiling a boot.img base on different boot.img
they also say that when i unpack it the command just discarded the garbage or other files
now my question is if theres any how would i know and where would i find the specific procedure of repacking my boo.imgs
and the missing files i think they were neccessary if there any missing file. how would i get it and how would i know what it is
my devices is running ics , cpu msm825, kernel 3.0..
this is my partition table and i dont understand any of it or which is which
i use abootimg and in boot.cfg this is whats written might be helpful
bootsize = 0xd42000
pagesize = 0x1000
kerneladdr = 0x208000
ramdiskaddr = 0x1508000
secondaddr = 0x1100000
tagsaddr = 0x200100
name =
cmdline = androidboot.hardware=qcom loglevel=1
in adb shell i ran
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 150 mmcblk0p2
179 3 40960 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 13576 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 466666 mmcblk0p12
179 13 1970176 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 102400 mmcblk0p15
179 16 13576 mmcblk0p16
179 17 20 mmcblk0p17
179 18 1048576 mmcblk0p18
179 19 1000 mmcblk0p19
179 20 111441 mmcblk0p20
179 32 1927168 mmcblk1
179 33 1926144 mmcblk1p1
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
debugfs /mnt/debugfs debugfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 ro,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:18 /mnt/emmc vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=continue 0 0
/dev/block/vold/179:33 /mnt/sdcard 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=continue 0 0
/dev/block/vold/179:33 /mnt/secure/asec 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=continue 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 170.7M 64.0K 170.7M 4096
/mnt/asec 170.7M 0.0K 170.7M 4096
/mnt/obb 170.7M 0.0K 170.7M 4096
/system 448.5M 375.4M 73.1M 4096
/data 1.8G 181.5M 1.7G 4096
/persist 9.8M 4.0M 5.8M 4096
/cache 98.4M 4.0M 94.4M 4096
/mnt/emmc 1013.6M 658.5M 355.1M 4096
/mnt/sdcard 1.8G 1.8G 9.1M 4096
/mnt/secure/asec 1.8G 1.8G 9.1M 4096
[email protected]:/ # ls -la
drwxr-xr-x root root 2013-12-23 18:04 acct
drwxrwx--x system cache 1970-01-01 08:00 cache
-rwxr-x--- root root 190772 1970-01-01 08:00 charger
dr-x------ root root 2013-12-23 18:04 config
lrwxrwxrwx root root 2013-12-23 18:04 d -> /sys/kernel/debug
drwxrwxr-x system system 2013-12-23 18:04 data
-rw-r--r-- root root 151 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-12-23 18:08 dev
lrwxrwxrwx root root 2013-12-23 18:04 emmc -> /mnt/emmc
lrwxrwxrwx root root 2013-12-23 18:04 etc -> /system/etc
-rwxr-x--- root root 182020 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 8772 1970-01-01 08:00 init.qcom.class_core.sh
-rwxr-x--- root root 4529 1970-01-01 08:00 init.qcom.class_main.sh
-rwxr-x--- root root 16886 1970-01-01 08:00 init.qcom.rc
-rwxr-x--- root root 4570 1970-01-01 08:00 init.qcom.sh
-rwxr-x--- root root 27316 1970-01-01 08:00 init.qcom.usb.rc
-rwxr-x--- root root 5512 1970-01-01 08:00 init.qcom.usb.sh
-rwxr-x--- root root 24437 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2680 1970-01-01 08:00 init.target.rc
drwxrwxr-x root system 2013-12-23 18:04 mnt
-rwxr-x--- root root 67104 1970-01-01 08:00 nv_set
drwxrwx--x system system 1970-01-01 08:00 persist
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwxr-xr-x root root 1970-01-01 08:00 res
-rwxr-x--- root root 63472 1970-01-01 08:00 rmt_storage_recovery
drwx------ root root 2013-01-22 10:18 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-12-23 18:04 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-12-23 18:04 sys
drwxrwxr-x root root 2013-12-22 06:15 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 9232 1970-01-01 08:00 ueventd.rc
lrwxrwxrwx root root 2013-12-23 18:04 vendor -> /system/vendor
can anyone help me with this?
Hi!
So I got a nice data2sd setup with f2fs on external data partition for some time. Yesterday I've found out I can't do $hit on my ext4 sdcardi. Today I checked that internal data partition is mounted as datai, not sdcardi. I've got some really easy questions for you guys. Don't want to check them empirically because I really like my current setup and ruining it would be disappointing. So here it goes.
1. I want to mount internal data partiotion as sdcardi rather than datai. Is modifying fstab,cardhu under / the only thing to change it? Aren't there any other references to internal data?
2. I want to format my internal data to f2fs instead of ext4. Again - would modifying fstab.cardhu under / be enough? I got Hunds latest kernel, will it deal with f2fs sdcardi?
3. Where did sdcardi come from? If internal data is mounet as datai why would I even have a sdcardi folder?
4. This one is just for curiosity. Doing anything on sdcardi fails (copying to, moving to, creating file/folder). Sdcard2 is sd card in dock, right? I never owned a dock, but yesterday I copied crombi-kk zip to sdcard2. It freezed around 62-64% and forced a reboot. How come doing stuff on non-existent sdcardi fails instantly, but doing stuff on non-existent sdcard2 fails during an operation? I don't even know what happens...
I'm just asking anyone willing to help to be fair on first two questions. I really want to avoid another full wipe.
EDIT Silly me, of course I meant fstab.cardhu under /. Second fact - modyfing this file won't do anything. I change datai to sdcardi, but on boot something reverts fstab to prevoius state, resulting in datai mounted. And one more thing - ES File Explorer correctly states sdcardi partition size - 56,5 GB (yeah, it's for sure internal data), some 180mb on it (dunno what it is)... Crap, I want my sdcardi back.
So one more question:
5. What operates on fstab.cardhu? Why does it change on boot? What defines its content? How to properly change mounting of internal data partition if modifying fstab.cardhu changes nothing?
wnerw said:
Hi!
So I got a nice data2sd setup with f2fs on external data partition for some time. Yesterday I've found out I can't do $hit on my ext4 sdcardi. Today I checked that internal data partition is mounted as datai, not sdcardi. I've got some really easy questions for you guys. Don't want to check them empirically because I really like my current setup and ruining it would be disappointing. So here it goes.
1. I want to mount internal data partiotion as sdcardi rather than datai. Is modifying fstab,cardhu under / the only thing to change it? Aren't there any other references to internal data?
2. I want to format my internal data to f2fs instead of ext4. Again - would modifying fstab.cardhu under / be enough? I got Hunds latest kernel, will it deal with f2fs sdcardi?
3. Where did sdcardi come from? If internal data is mounet as datai why would I even have a sdcardi folder?
4. This one is just for curiosity. Doing anything on sdcardi fails (copying to, moving to, creating file/folder). Sdcard2 is sd card in dock, right? I never owned a dock, but yesterday I copied crombi-kk zip to sdcard2. It freezed around 62-64% and forced a reboot. How come doing stuff on non-existent sdcardi fails instantly, but doing stuff on non-existent sdcard2 fails during an operation? I don't even know what happens...
I'm just asking anyone willing to help to be fair on first two questions. I really want to avoid another full wipe.
EDIT Silly me, of course I meant fstab.cardhu under /. Second fact - modyfing this file won't do anything. I change datai to sdcardi, but on boot something reverts fstab to prevoius state, resulting in datai mounted. And one more thing - ES File Explorer correctly states sdcardi partition size - 56,5 GB (yeah, it's for sure internal data), some 180mb on it (dunno what it is)... Crap, I want my sdcardi back.
So one more question:
5. What operates on fstab.cardhu? Why does it change on boot? What defines its content? How to properly change mounting of internal data partition if modifying fstab.cardhu changes nothing?
Click to expand...
Click to collapse
Hmm you have a lot of questions and a lot to learn
In a sensible order. Fstab.cardhu comes from the kernel ramdisk. You can't edit files in the ramdisk without repacking the kernel and flashing it. So in this case on every boot the kernel replaces your version with its version. I'm not going to explain kernel packing as it's a large topic but happy to answer questions if you look up blob packer and ramdisk repacking. Typically you'll need a Linux setup or cygwin on windows to do it.
/datai represents the whole internal data partition. This is not the same as sdcardi which represents your internal sdcard area. Which is /datai/media/0 - the area where your media stuff goes.
They are both setup in init.cardhu.rc first again in the ramdisk. Have a look and you will see it. The fstab sets the mount points and type of partitions.
I personally wouldn't rename them but of course you could rename them whatever you want. Typically you don't want to write to datai as it belongs to your internal ROM. sdcardi should be rw already but if not mount it rw first. You can write to this safely.
sbdags said:
Hmm you have a lot of questions and a lot to learn
In a sensible order. Fstab.cardhu comes from the kernel ramdisk. You can't edit files in the ramdisk without repacking the kernel and flashing it. So in this case on every boot the kernel replaces your version with its version. I'm not going to explain kernel packing as it's a large topic but happy to answer questions if you look up blob packer and ramdisk repacking. Typically you'll need a Linux setup or cygwin on windows to do it.
/datai represents the whole internal data partition. This is not the same as sdcardi which represents your internal sdcard area. Which is /datai/media/0 - the area where your media stuff goes.
They are both setup in init.cardhu.rc first again in the ramdisk. Have a look and you will see it. The fstab sets the mount points and type of partitions.
I personally wouldn't rename them but of course you could rename them whatever you want. Typically you don't want to write to datai as it belongs to your internal ROM. sdcardi should be rw already but if not mount it rw first. You can write to this safely.
Click to expand...
Click to collapse
Well, so my problems split into two different topics. For the first one there is only one question. In general - repacking ramdisk would be enough for me to use internal data with f2fs? That is what I understand from your post. I have to repack to change fstab, and insisde fstab I need to change datai fs to f2fs...
And the other one, more urgent... I can't write to sdcardi. I have a data2sd setup, so datai doesn't really work as data for internal rom, as I don't have internal rom. I really need this internal partition mounted as rw, I have $hitload of docs, and they won't fit into any of external partitions, as I have $hitload of apps
Sorry for bothering you, but I got so confused trying to follow all this mounts and symlikns... It was so easy on CROMi-X I don't even know how to troubleshoot this problem now. All I know is that sdcardi is empty and inaccessible in any way from ES FIle Explorer, although this app shows sdcardis size properly. Under datai there is one folder I successfully created and /media. Under media there is TWRP folder. Keeping internal data mounted as datai seems to be good, as you suggested. Still, I need sdcardi to be rw for my files.
EDIT CM File Explorer, the one built in, can't even open sdcardi. It suggests that I try using root access, but I already gave it root priviliges...
EDIT2 After "su", Terminal Emulator let me into sdcardi, but on ls usage it says "opendir failed, Permission denied". What the heck, su is not enough?
wnerw said:
Well, so my problems split into two different topics. For the first one there is only one question. In general - repacking ramdisk would be enough for me to use internal data with f2fs? That is what I understand from your post. I have to repack to change fstab, and insisde fstab I need to change datai fs to f2fs...
And the other one, more urgent... I can't write to sdcardi. I have a data2sd setup, so datai doesn't really work as data for internal rom, as I don't have internal rom. I really need this internal partition mounted as rw, I have $hitload of docs, and they won't fit into any of external partitions, as I have $hitload of apps
Sorry for bothering you, but I got so confused trying to follow all this mounts and symlikns... It was so easy on CROMi-X I don't even know how to troubleshoot this problem now. All I know is that sdcardi is empty and inaccessible in any way from ES FIle Explorer, although this app shows sdcardis size properly. Under datai there is one folder I successfully created and /media. Under media there is TWRP folder. Keeping internal data mounted as datai seems to be good, as you suggested. Still, I need sdcardi to be rw for my files.
EDIT CM File Explorer, the one built in, can't even open sdcardi. It suggests that I try using root access, but I already gave it root priviliges...
EDIT2 After "su", Terminal Emulator let me into sdcardi, but on ls usage it says "opendir failed, Permission denied". What the heck, su is not enough?
Click to expand...
Click to collapse
You'll have repack the fstab intontne kernel ramdisk yes if you to have both data and datai as f2fs.
Su just gives root permissions. You still need to mount it as rw but the kernel should have done that for you. I'm not back from my holiday until next week so you'll have to wait until I can look into it.
---------- Post added at 01:55 PM ---------- Previous post was at 01:43 PM ----------
Try this in a terminal
mount -ro remount,rw /sdcardi
sbdags said:
You'll have repack the fstab intontne kernel ramdisk yes if you to have both data and datai as f2fs.
Su just gives root permissions. You still need to mount it as rw but the kernel should have done that for you. I'm not back from my holiday until next week so you'll have to wait until I can look into it.
---------- Post added at 01:55 PM ---------- Previous post was at 01:43 PM ----------
Try this in a terminal
mount -ro remount,rw /sdcardi
Click to expand...
Click to collapse
Thanks for advice on fstab
Typing that command in terminal gives no results. No output to terminal, no effect. Typing only mount to terminal gives this:
Code:
rootfs / rootfs ro,relatime 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
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
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/se.feomedia.quizkampen.pl.premium-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/de.tsorn.FullScreenPlus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 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/mmcblk0p1 /system ext4 ro,relatime,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
/dev/block/mmcblk1p2 /data f2fs rw,relatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.browser_cache /data/data/com.android.browser/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/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,data=writeback,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
/dev/fuse /storage/sdcardi fuse ro,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:49 /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/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Maybe something is wrong here. I dunno, this doesn't tell me much. I can pull some logcats if thats necessary.
Well, enjoy your holiday I'll focus on something else, Easter probably, and come back to this issue when you do. Unless some other clever people might help me, there are so many of you on tf700 forum...
wnerw said:
In general - repacking ramdisk would be enough for me to use internal data with f2fs?
Click to expand...
Click to collapse
You need to format the partition with the same filesystem as specified in fstab. Also remember to remove the ext4-specific mount options.
wnerw said:
And the other one, more urgent... I can't write to sdcardi. I have a data2sd setup, so datai doesn't really work as data for internal rom, as I don't have internal rom.
Click to expand...
Click to collapse
If you have never set up any internal ROM, maybe your internal /data/media/0 directory doesn't even exist.
wnerw said:
Sorry for bothering you, but I got so confused trying to follow all this mounts and symlikns... It was so easy on CROMi-X
Click to expand...
Click to collapse
It *is* confusing.
wnerw said:
I don't even know how to troubleshoot this problem now.
Click to expand...
Click to collapse
By using "ls" and "mount".
wnerw said:
All I know is that sdcardi is empty and inaccessible in any way from ES FIle Explorer, although this app shows sdcardis size properly. Under datai there is one folder I successfully created and /media. Under media there is TWRP folder. Keeping internal data mounted as datai seems to be good, as you suggested. Still, I need sdcardi to be rw for my files.
Click to expand...
Click to collapse
If there is no "0" in /data/media, maybe that's really the problem.
wnerw said:
Code:
/dev/block/mmcblk1p2 /data f2fs rw,relatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0
/dev/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,data=writeback,noauto_da_alloc,discard 0 0
Click to expand...
Click to collapse
These two are the external and internal /data partitions.
wnerw said:
Code:
/dev/fuse /storage/sdcardi fuse ro,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Click to expand...
Click to collapse
Note that this one is read-only. Check if /sdcardi points to this (ls -l /), and how this fuse filesystem was started (look in /init.*rc for /storage/sdcardi and check the other path passed to the sdcard daemon).
Aww yiss, @_that aswered mah post...
Good. I will repack ramdisk. I mill just wait till Easter ends, I don't want to spend it with my pc instead of family
Oh, I've set up internal rom many times. I just full wipe every time. I've created 0 under /datai/media. Didn't help.
ls -l / gave this:
Code:
drwxr-xr-x root root 2014-04-17 23:08 acct
drwxrwx--x system cache 2014-04-05 19:39 cache
dr-x------ root root 2014-04-17 23:08 config
lrwxrwxrwx root root 2014-04-17 23:08 d -> /sys/kernel/debug
drwxrwx--x system system 2014-04-17 23:09 data
drwxr-xr-x root root 2014-04-17 08:59 datai
-rw-r--r-- root root 161 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2014-04-17 23:10 dev
lrwxrwxrwx root root 2014-04-17 23:08 etc -> /system/etc
-rw-r--r-- root root 10678 1970-01-01 01:00 file_contexts
-rw-r--r-- root root 1978 1970-01-01 01:00 fstab.cardhu
-rwxr-x--- root root 183792 1970-01-01 01:00 init
-rwxr-x--- root root 2185 1970-01-01 01:00 init.cardhu.cpu.rc
-rwxr-x--- root root 58 1970-01-01 01:00 init.cardhu.keyboard.rc
-rwxr-x--- root root 19924 1970-01-01 01:00 init.cardhu.rc
-rwxr-x--- root root 3012 1970-01-01 01:00 init.cardhu.usb.rc
-rwxr-x--- root root 6159 1970-01-01 01:00 init.cm.rc
-rwxr-x--- root root 956 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 21902 1970-01-01 01:00 init.rc
-rwxr-x--- root root 670 1970-01-01 01:00 init.recovery.cardhu.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- root root 1795 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 01:00 init.usb.rc
drwxrwxr-x root system 2014-04-17 23:08 mnt
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2161 1970-01-01 01:00 property_contexts
drwx------ root root 2014-02-13 09:42 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 2014-04-17 23:08 sdcard -> /storage/emulated/legacy
lrwxrwxrwx root root 2014-04-17 23:08 sdcardi -> /storage/sdcardi
-rw-r--r-- root root 656 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 77015 1970-01-01 01:00 sepolicy
drwxr-x--x root sdcard_r 2014-04-17 23:08 storage
drwxr-xr-x root root 2014-04-17 23:08 sys
drwxr-xr-x root root 2014-04-14 14:36 system
-rw-r--r-- root root 2501 1970-01-01 01:00 ueventd.cardhu.rc
-rw-r--r-- root root 5896 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 2014-04-17 23:08 vendor -> /system/vendor
I think it's nothing new. sdcardi with all permissions, but inaccessible.
Only init.cardhu.rc points to sdcardi, in two places:
Code:
# Data2SD
# mkdir /storage/emulated/internal
# symlink /storage/emulated/internal/0 /storage/sdcardi
mkdir /datai
mkdir /storage/sdcardi
symlink /storage/sdcardi /mnt/sdcardi
symlink /storage/sdcardi /sdcardi
Code:
service sdcardi /system/bin/sdcard -u 1023 -g 1023 -l /datai/media /storage/sdcardi
class late_start
I don't see anything helpful here either. Well, I don't but maybe it is...
/dev/fuse doesn't appear in any of init.*rc
Well, this is 99% pure setup, made after full wipe. It either rom issue to be solved with future update or...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wnerw said:
I think it's nothing new. sdcardi with all permissions, but inaccessible.
Click to expand...
Click to collapse
sdcardi is a symlink; symlinks always have all permissions. Check the permissions of the link's target.
wnerw said:
Code:
symlink /storage/sdcardi /sdcardi
Code:
service sdcardi /system/bin/sdcard -u 1023 -g 1023 -l /datai/media /storage/sdcardi
class late_start
I don't see anything helpful here either. Well, I don't but maybe it is...
Click to expand...
Click to collapse
It is at least helpful to understand the problem better. The sdcard daemon uses the fuse subsystem to allow access to the files stored in /datai/media (with special simulated permissions and disabled case sensitivity) via /storage/sdcardi, which is the target of the symlink /sdcardi.
Now the open question is why /storage/sdcardi is mounted as read-only and what happens if you remount that rw.
So here goes some more ls -l...
Code:
[email protected]:/ # ls -l storage
d---r-x--- root sdcard_r 2014-04-17 23:10 emulated
lrwxrwxrwx root root 2014-04-17 23:08 sdcard0 -> /storage/emulated/legacy
drwxrwx--x root sdcard_r 1970-01-01 01:00 sdcard1
drwx------ root root 2014-04-17 23:08 sdcard2
drwxrwx--x root sdcard_r 2014-04-17 23:08 sdcardi
drwx------ root root 2014-04-17 23:08 usbdisk0
drwx------ root root 2014-04-17 23:08 usbdisk1
[email protected]:/ # ls -l datai
drwx------ root root 2014-04-17 08:59 Folder
drwxrwx--- root root 2014-04-17 23:08 media
[email protected]:/ # ls -l datai/media
drwxrwxrwx root root 2014-04-18 00:46 0
drwxrwxrwx root root 2014-04-05 17:31 TWRP
Note that 0 is created by me, I changed its permissions after it gave no solution. I also created a file under 0, but it doesn't appear under sdcardi. I'm getting sleepy and confused, it's 1 am here... I really apreciate your help guys. I'm eager to keep solving this.
EDIT I have no idea which of my actions did this, but /dev/fuse for storage/sdcardi changed to rw, here:
Code:
rootfs / rootfs ro,relatime 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
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
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/se.feomedia.quizkampen.pl.premium-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/de.tsorn.FullScreenPlus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 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/mmcblk0p1 /system ext4 ro,relatime,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
/dev/block/mmcblk1p2 /data f2fs rw,relatime,background_gc=on,discard,user_xattr,acl,errors=panic,active_logs=6 0 0
com.android.browser_cache /data/data/com.android.browser/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/block/mmcblk0p8 /datai ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,user_xattr,acl,barrier=0,data=writeback,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
/dev/fuse /storage/sdcardi fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:49 /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/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
But the problem still persists, I can't write to sdcardi.
wnerw said:
But the problem still persists, I can't write to sdcardi.
Click to expand...
Click to collapse
Same problem here. Somehow I found that /datai/media/ is writable, you may use it instead.
UPDATE: This is an issue of permission. Changing the owner of /datai/media/ will make it work.
wenchien said:
Same problem here. Somehow I found that /datai/media/ is writable, you may use it instead.
UPDATE: This is an issue of permission. Changing the owner of /datai/media/ will make it work.
Click to expand...
Click to collapse
To what owner did you change it? I can't check stuff right now, just came back to my home from a trip.
wnerw said:
To what owner did you change it? I can't check stuff right now, just came back to my home from a trip.
Click to expand...
Click to collapse
I changed it to the same PID:GID with /data/media (which is media_rw:media_rw).
I've got a fancy new Asus K01A and as far as I can tell, I'm the first to try to root it on xda, or at least the first to try to make CWM for it. When you're making CWM, it's rather important to know exactly where the recovery partitition is, in case I need to flash something from fastboot to correct something stupid it did. Problem is, I can't seem to find a partition for recovery, here's a bunch of partition information I gathered:
/proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 48128 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 21504 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 21504 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 428032 mmcblk0p8
179 9 1187840 mmcblk0p9
259 0 13633519 mmcblk0p10
179 40 4096 mmcblk0rpmb
179 30 8192 mmcblk0gp0
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 3872256 mmcblk1
179 51 3870720 mmcblk1p1
"$ mount" results
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
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=700,uid=1023,gid=1023 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=751,gid=1028 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/intel/by-label/system /system ext4 ro,seclabel,noatime,data=
ordered 0 0
/dev/block/platform/intel/by-label/factory /factory ext4 ro,seclabel,noatime 0 0
/dev/block/platform/intel/by-label/cache /cache ext4 rw,seclabel,nosuid,nodev,no
atime,data=ordered 0 0
/dev/block/platform/intel/by-label/config /config ext4 rw,seclabel,nosuid,nodev,
noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/firmware /firmware ext4 ro,seclabel,noatime,d
ata=ordered 0 0
/dev/block/platform/intel/by-label/data /data ext4 rw,seclabel,nosuid,nodev,noat
ime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/intel/by-label/gauge /gauge ext4 rw,seclabel,nosuid,nodev,no
atime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p7 /ADF ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /pstore pstore rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:51 /mnt/media_rw/MicroSD vfat rw,dirsync,nosuid,nodev,noexec
,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:51 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/MicroSD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/platform/intel/by-label contents
lrwxrwxrwx root root 2014-11-28 17:29 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 cache -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 config -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 data -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-28 17:29 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 firmware -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 gauge -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 system -> /dev/block/mmcblk0p9
/dev/block/platform/intel/by-guid contents
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000000 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000001 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000002 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000003 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000004 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000005 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000006 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000007 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000008 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000009 -> /dev/block/mmcblk0p10
Parted info for partitions
Model: MMC 016GE2 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 49.3MB 49.3MB reserved boot
2 49.3MB 57.7MB 8389kB panic boot
3 57.7MB 59.8MB 2097kB ext2 factory
4 59.8MB 81.8MB 22.0MB ext4 config
5 81.8MB 82.9MB 1049kB ext2 gauge
6 82.9MB 105MB 22.0MB ext4 firmware
7 105MB 138MB 33.6MB ext4 ADF
8 138MB 577MB 438MB ext4 cache
9 577MB 1793MB 1216MB ext4 system
10 1793MB 15.8GB 14.0GB ext4 data
I'm wondering if somehow there is a specific file or if the recovery is somehow integrated into the bootloader. If so, my hopes are dashed :crying:
Hi,
I would ask if anyone knows anything here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Hello guyz...
Can someone tell me how to take EFS backup via Terminal Emulator in Core i8262 ?
Plz help...
EFS
vatsalbh9 said:
Hello guyz...
Can someone tell me how to take EFS backup via Terminal Emulator in Core i8262 ?
Plz help...
Click to expand...
Click to collapse
This has to be done like this way :
If's for GC2, on Core i826 it will be similar :
1. find out where EFS is mounted :
You can try it with mount (U'll need SU acess) and then search for efs :
Code:
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,mode=700 0 0
/dev/block/vold/179:129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/nextapp.fx.rk-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
[COLOR="Red"][B]/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0[/B][/COLOR]
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:129 /mnt/media_rw/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
or just plain ls :
Code:
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 2014-11-10 14:25 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-10 14:25 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-10 14:25 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-11-10 14:25 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-11-10 14:25 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-10 14:25 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-10 14:25 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-10 14:25 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-11-10 14:25 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-11-10 14:25 RECOVERY -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-11-10 14:25 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-10 14:25 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-10 14:25 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-10 14:25 WDSP_BACKUP -> /dev/block/mmcblk0p6
[B][COLOR="Red"]lrwxrwxrwx root root 2014-11-10 14:25 efs -> /dev/block/mmcblk0p14[/COLOR][/B]
lrwxrwxrwx root root 2014-11-10 14:25 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-11-10 14:25 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-11-10 14:25 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-11-10 14:25 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-11-10 14:25 userdata -> /dev/block/mmcblk0p22
so now u know it's in /dev/block/platform/sprd-sdhci.3/by-name/efs or it equals /dev/block/mmcblk0p14
Code:
ls -l /dev/block/platform/sprd-sdhci.3/by-name/efs
lrwxrwxrwx root root 2015-03-10 22:16 efs -> /dev/block/mmcblk0p14
now just need to copy it to the extSdCard :
Code:
[email protected]:/ # cat /dev/block/platform/sprd-sdhci.3/by-name/efs>/storage/extSdCard/EFS
or dd:
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/EFS bs=2048
f=/storage/extSdCard/EFS bs=2048
10240+0 records in
10240+0 records out
20971520 bytes transferred in 0.664 secs (31583614 bytes/sec)
Now you have a backup.
Regards
StratOS_HTC said:
This has to be done like this way :
If's for GC2, on Core i826 it will be similar :
1. find out where EFS is mounted :
You can try it with mount (U'll need SU acess) and then search for efs :
Code:
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,mode=700 0 0
/dev/block/vold/179:129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/nextapp.fx.rk-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,errors=continue 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
[COLOR="Red"][B]/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0[/B][/COLOR]
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:129 /mnt/media_rw/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/media_rw/extSdCard /storage/extSdCard sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=unified 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
or just plain ls :
Code:
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 2014-11-10 14:25 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-10 14:25 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-10 14:25 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-11-10 14:25 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-11-10 14:25 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-10 14:25 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-10 14:25 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-10 14:25 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-11-10 14:25 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-11-10 14:25 RECOVERY -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-11-10 14:25 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-10 14:25 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-10 14:25 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-10 14:25 WDSP_BACKUP -> /dev/block/mmcblk0p6
[B][COLOR="Red"]lrwxrwxrwx root root 2014-11-10 14:25 efs -> /dev/block/mmcblk0p14[/COLOR][/B]
lrwxrwxrwx root root 2014-11-10 14:25 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-11-10 14:25 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-11-10 14:25 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-11-10 14:25 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-11-10 14:25 userdata -> /dev/block/mmcblk0p22
so now u know it's in /dev/block/platform/sprd-sdhci.3/by-name/efs or it equals /dev/block/mmcblk0p14
Code:
ls -l /dev/block/platform/sprd-sdhci.3/by-name/efs
lrwxrwxrwx root root 2015-03-10 22:16 efs -> /dev/block/mmcblk0p14
now just need to copy it to the extSdCard :
Code:
[email protected]:/ # cat /dev/block/platform/sprd-sdhci.3/by-name/efs>/storage/extSdCard/EFS
or dd:
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/EFS bs=2048
f=/storage/extSdCard/EFS bs=2048
10240+0 records in
10240+0 records out
20971520 bytes transferred in 0.664 secs (31583614 bytes/sec)
Now you have a backup.
Regards
Click to expand...
Click to collapse
So finaally i have write which code in Emulator ?
This one ? "dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/EFS bs=2048
f=/storage/extSdCard/EFS bs=2048" ?
Exactly as it is ?
vatsalbh9 said:
So finaally i have write which code in Emulator ?
This one ? "dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/EFS bs=2048
f=/storage/extSdCard/EFS bs=2048" ?
Exactly as it is ?
Click to expand...
Click to collapse
It's stated.
First :
Code:
su
mount
(You must be rooted)
or
Code:
-l /dev/block/platform/*/by-name/
and look for where EFS is mounted
and then make a backup of EFS location via cat or dd.Replace the PATH with EFS location you get in previous execution.
Code:
cat PATH>/storage/extSdCard/EFS
or
Code:
dd if=PATH of=/storage/extSdCard/EFS bs=2048