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).
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 think I made a mistake trying to use adb shell.
Was able to get my Evo shift 4G rooted. That went smoothly first try. Did the steps manually. Wanted to downgrade to 2.2 from 2.3.3
Was trying to copy misc.img to SD card root
adb push misc.img /sdcard
Click to expand...
Click to collapse
and it seems to have copied misc.img to a file called sdcard overwriting whatever was there before. Sorry for the noob question, but was the sdcard file a file that tells how to mount the sdcard device?
C:\SDK\platform-tools>adb shell mount /sdcard
adb server is out of date. killing...
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Click to expand...
Click to collapse
Seems like mounting sdcard fails
# dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
/sdcard/misc.img: cannot open for read: Not a directory
Click to expand...
Click to collapse
# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
/dev/block/mmcblk0p26 /system ext3 ro,relatime,errors=continue,barrier=0,data=or
dered 0 0
/dev/block/mmcblk0p27 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrie
r=0,data=ordered 0 0
/dev/block/mmcblk0p28 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barri
er=0,data=ordered 0 0
/dev/block/mmcblk0p31 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,barr
ier=0,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow
_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
C:\SDK\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT16RHV04001 device
Click to expand...
Click to collapse
C:\SDK\platform-tools>adb shell ls -l
adb server is out of date. killing...
* daemon started successfully *
-rw-rw-rw- root root 262144 2011-03-17 10:14 misc.img
-rw-rw-rw- root root 262144 2011-03-17 10:14 sdcard
drwxrwxrwx root root 2011-12-10 20:36 vendor
drwxr-xr-x root system 2011-12-10 14:53 app-cache
dr-x------ root root 2011-12-10 14:51 config
drwxr-xr-x root root 2011-12-10 14:51 acct
drwxrwxr-x root system 2011-12-10 14:51 mnt
lrwxrwxrwx root root 2011-12-10 14:51 etc -> /system/etc
drwx------ root root 2011-12-10 19:54 devlog
drwxrwx--- system cache 2011-12-10 21:55 cache
-rw-r--r-- root root 758 1969-12-31 19:00 ueventd.speedy.rc
-rw-r--r-- root root 4311 1969-12-31 19:00 ueventd.rc
-rw-r--r-- root root 0 1969-12-31 19:00 ueventd.goldfish.rc
drwxr-xr-x root root 2011-09-09 00:38 system
drwxr-xr-x root root 2011-12-10 14:51 sys
drwxr-x--- root root 1969-12-31 19:00 sbin
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rwxr-x--- root root 6118 1969-12-31 19:00 init.speedy.rc
-rwxr-x--- root root 20031 1969-12-31 19:00 init.rc
-rwxr-x--- root root 1677 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 103156 1969-12-31 19:00 init
-rw-r--r-- root root 118 1969-12-31 19:00 default.prop
drwxrwx--x system system 2011-11-15 19:16 data
-rw-r--r-- root root 1398 1969-12-31 19:00 cwkeys
-rw-r--r-- root root 460 1969-12-31 19:00 bootcomplete.rc
drwx------ root root 2011-05-24 07:42 root
drwxr-xr-x root root 2011-12-10 20:14 dev
Click to expand...
Click to collapse
How can I fix my mistake? I tried Ext2explore to read PG06IMG looking for the file, but I didn't find it.
Looks like you did . Did you have a backup copy of the card?
After some more reading, I figured out things were not working correctly. (Well obviously. lol) Not sure what the file called sddisk was, but I just deleted it. The path to the files on the sd card, was actually at... /mnt/sdcard/
I modified this line...
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Click to expand...
Click to collapse
To
dd if=/mnt/sdcard/misc.img of=/dev/block/mmcblk0p17
Click to expand...
Click to collapse
and the command worked.
After I did that, the rest of the downgrade to 2.2 worked well. I'm happy.
Another strange occurrence. There was another instruction.
rm vendor
Click to expand...
Click to collapse
This wouldn't work for me. got the error. 'rm' is only for files, not directories. i had to use the command 'rmdir' on the empty directory.
In the end I do have success with the downgrade. permanent root.
Well glad you got it sorted out.
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?
Hello all. Long time lurker, occasional poster - hope you can help me out here.
So, I came from a stock rooted Pixel running the June security update, and recently moved everything over to a combo of Stock ROM + ElementalX kernel + Magisk v12 with some help from a handy guide here on the forums.
To my chagrin, I noticed that StickMount Pro no longer functioned with MagiskSU. Not that big of a deal - I learned to live without.
*However*
Now I seem to be unable to delete the sdcard directory tree starting at /sdcard/usbStorage/, regardless of what all I've thrown at it.
In the terminal, each folder/subfolder looks like this: (ls -al)
Code:
. . .
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 sda4
. . .
There's notably just sda4 - sda36, skipping a few between, then sdb1, sdc1, sdd2 - sdd 13.
There's these folders under /sdcard/usbStorage/ : (ls -al)
Code:
.
. .
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:13 00BC-614E
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 _
. . .
One of those looks like a device's UUID.
I've tried:
- Removing with SolidExplorer, and as root.
- su rm -rf /sdcard/usbStorage (received permission denied errors)
- su; busybox rm -rf /sdcard/usbStorage (just for completeness)
- Reinstalling StickMount and trying the various unmount options, as well as unticking the "create /sdcard/ directories" option
Since these failed me, I began trying to change the folder/group permissions across adb:
- chown -R 777 /sdcard/usbStorage , then rm -rf (still permission denied)
- addgroup $(whoami) sdcard_rw (unknown user "root")
- addgroup root sdcard_rw (unknown user "root")
The `mount` command lists nothing related. Only the following:
Code:
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1896652k,nr_inodes=474163,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/sda25 on /firmware/radio type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sdd3 on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1896652k,nr_inodes=474163,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/sda35 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
/dev/block/loop0 on /magisk type ext4 (rw,seclabel,noatime,data=ordered)
/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)
tmpfs on /system/xbin type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
tmpfs on /sbin type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Also, any attempt to mount/umount things throws the error:
Code:
mount: bad /etc/fstab: No such file or directory
etc...
I'm just hesitant to re-install SuperSU for fear of how it will clash with TWRP and Magisk *and* break SafetyNet just to try to remove this dir.
Could these somehow be related to the /dev/fuse filesystems?
Any help at all would be appreciated.
If I can't effectively chown / chmod them, I don't quite know how to proceed.
Thanks!
/dev/block/mmcblk0p35 /3rdmodem ext4 rw 0 0
/dev/block/mmcblk0p36 /cache ext4 rw 0 0
/dev/block/mmcblk0p44 /cust ext4 rw 0 0
/dev/block/dm-0 /data f2fs rw 0 0
/dev/block/mmcblk0p43 /system ext4 rw 0 0
/dev/block/mmcblk0p46 /vendor ext4 rw 0 0
/dev/block/mmcblk0p47 /product ext4 rw 0 0
/dev/block/mmcblk1p1 /external_sd exfat rw 0 0
/usbotg auto rw 0 0
Just what I thought. I have a different mmcblk0p**.
hdc said:
Just what I thought. I have a different mmcblk0p**.
Click to expand...
Click to collapse
Ok. Glad I could help.
Have a nice one!
Thanks, @nortish, can you give me also:
ls /dev/block/
and
ls /dev/block/bootdevice/by-name
?
Gonna try to post that later. No time atm.
Sent from my FRD-L09 using Tapatalk
Sorry @hdc that I forgot to answer. Hope you got it sorted anyway =)
Sent from my FRD-L09 using Tapatalk