Problem with External Storage - Xperia Tablet Z Q&A, Help & Troubleshooting

I'm having problems with my external storage (sdcard1). It was working fine unrooted, but now that I'm rooted I'm unable to use it. Depending upon which path I follow (using ES Explorer in root mode), I get the message "file.txt cannot be deleted" or "read-only file system". I have no problems writing to the card in Linux or Windows.
For troubleshooting, I try to create a Folder and then a File. I previously added a test folder and test file via Windows Explorer.
Path selected via ES Explorer: /storage/sdcard1/
Try to add folder, received error message: The folder(file) will not be created. Sorry operation failed.
Try to delete test file(folder), receive error message: test1.txt cannot be deleted.
Path selected via ES Explorer: /storage/removable/sdcard1 ('sdcard1' in /storage/removable/ symlinks to /storage/sdcard1/)
Try to add folder received error message: The folder(file) will not be created. Sorry operation failed.
Try to delete test file(folder, receive error message: read-only filesystem
Also, in adb shell, trying to create or delete a file results in 'rm: Test1: Read-only file system' error message. However, mount shows it is a rw filesystem.
As a novice, it looks like the wrong group is assigned to the sdcard1, compared to the permissions of platform.xml. For example, a complete directory listing of /storage/sdcard1/ shows the group owner to be sdcard_r. While platform.xml lists that group under anything with "EXTERNAL_STORAGE" in the name, it is missing from "WRITE_MEDIA_STORAGE". I suppose I could add that group and see if it fixes things, but the whole "ro filesystem" message has me wondering.
Some code (I truncated some of it to shorten the post).....
Code:
[email protected]:/ # pwd
/
[email protected]:/ # ls -la
drwxr-xr-x root root 1972-02-11 01:23 acct
drwxrwx--- system cache 1972-02-11 01:23 cache
lrwxrwxrwx root root 1969-12-31 18:00 charger -> /sbin/healthd
lrwxrwxrwx root root 1972-02-11 01:23 etc -> /system/etc
-rw-r--r-- root root 47853 1969-12-31 18:00 file_contexts
drwxrwx--x system system 1972-02-11 01:23 firmware
-rw-r--r-- root root 475 1969-12-31 18:00 fstab
-rw-r----- root root 1445 1969-12-31 18:00 fstab.qcom
drwxr-xr-x root root 1969-12-31 18:00 lta-label
drwxrwxr-x root system 1972-02-11 01:23 mnt
lrwxrwxrwx root root 1972-02-11 01:23 sdcard -> /storage/emulated/legacy
lrwxrwxrwx root root 1972-02-11 01:23 sdcard1 -> /storage/sdcard1
drwxr-x--x root sdcard_r 1972-02-11 01:23 storage
dr-xr-xr-x root root 1972-02-11 01:23 sys
drwxr-xr-x root root 2015-07-26 17:39 system
lrwxrwxrwx root root 1972-02-11 01:23 usbdisk -> /storage/usbdisk
lrwxrwxrwx root root 1972-02-11 01:23 vendor -> /system/vendor
[email protected]:/ # cd storage/
[email protected]:/storage # ls -la
d---r-x--- root sdcard_r 2015-07-31 17:45 emulated
d---r-x--- system removable_rw 1972-02-11 01:23 removable
lrwxrwxrwx root root 1972-02-11 01:23 sdcard0 -> /storage/emulated/legacy
drwxrwx--x root sdcard_r 1969-12-31 18:00 sdcard1
drwx------ system system 1972-02-11 01:23 usbdisk
[email protected]:/storage # cd sdcard1
[email protected]:/storage/sdcard1 # ls -la
lstat './.android_secure' failed: Permission denied
drwxrwx--x root sdcard_r 2015-07-29 20:26 Android
drwxrwx--- root sdcard_r 2015-07-29 20:28 DCIM
drwxrwx--- root sdcard_r 2015-07-29 21:20 Documents
lstat './LOST.DIR' failed: I/O error
drwxrwx--- root sdcard_r 2015-07-29 20:29 Media
drwxrwx--- root sdcard_r 2015-07-27 20:47 Misc
drwxrwx--- root sdcard_r 2015-07-29 21:34 Music
drwxrwx--- root sdcard_r 2015-07-29 21:28 OpenVPN
drwxrwx--- root sdcard_r 2015-07-29 21:28 Pictures
drwxrwx--- root sdcard_r 2015-07-31 17:20 Test1
drwxrwx--- root sdcard_r 2015-07-30 00:23 Videos
drwxrwx--- root sdcard_r 2009-01-02 12:00 XZDualRecovery
drwxrwx--- root sdcard_r 2015-07-29 20:28 bluetooth
-rwxrwx--- root sdcard_r 145 2015-07-29 20:34 customized-capability.xml
drwxrwx--- root sdcard_r 2015-07-30 02:00 data
-rwxrwx--- root sdcard_r 14335 2015-07-29 20:34 default-capability.xml
drwxrwx--- root sdcard_r 2015-07-29 21:21 downloads
drwxrwx--- root sdcard_r 2015-07-29 21:27 mysword
-rwxrwx--- root sdcard_r 0 2015-07-31 17:21 test1.txt
[email protected]:/storage/sdcard1 #
Output from mount....
Code:
[email protected]:/storage/sdcard1 # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/loop0 /system/odex squashfs ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:34 /data/sdext2 ext2 rw,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,context=u:object_r:lta_label:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
tmpfs /mnt/qcks tmpfs rw,seclabel,relatime,mode=770,uid=1000,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat ro,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,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
[email protected]:/storage/sdcard1 #
Relevant sections of platform.xml....
Code:
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>
I've included what I think is the relevant code. Just to rule it out, this is a brand new SD card. I replaced my last one because I thought there was a problem with it writing. Can someone help me figure this out? Thanks.

I've faced the same problems in my S4 and I'll suggest what I've done to solve it: take a full data and system backups from recovery, then wipe data and reinstall the Rom. Which rom are you in that is having such problems? FYI, my tab is on the pre rooted 502 rom made by myself and is not having such issues. Good luck buddy

Related

[Q] Check device Mount point mapping?

Hi,
Can anyone please tell me how I may check the mount point mappings for my phone?
All i can understand is /system is /dev/block/mmcblk0p3"
but how do check for the rest?
I already tried the following commands in terminal emulator but they didn't help:
mount
/proc/partitions
How did those commands not help? What was their output?
Maybe try
cat/proc/partitions
Or
ls -l /dev/block
Or
df
busybox df -hm
Also try with superuser permission, normally I do this in adb shell but terminal should work just fine
Sent from my Nexus 4 using xda premium
ibshar said:
Hi,
Can anyone please tell me how I may check the mount point mappings for my phone?
All i can understand is /system is /dev/block/mmcblk0p3"
but how do check for the rest?
I already tried the following commands in terminal emulator but they didn't help:
mount
/proc/partitions
Click to expand...
Click to collapse
To find out the rest of the mount points and block partition layouts from either terminal or adb shell run the following commands (Make sure to run the commands as root):
First:
Code:
cd /dev/block/platform
Next type:
Code:
ls
And you should see a platform name for example on my Nexus 10 it's dw_mmc.0 cd into the platform name directory (For example):
Code:
cd dw_mmc.0
Then after you have done that cd into the by-name directory:
Code:
cd by-name
And finally once in the by-name directory run the command:
Code:
ls -l
Which should produce an output similar to the following giving you a complete list of mount points and partition block layout:
Code:
lrwxrwxrwx root root 2013-07-25 12:35 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 12:35 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-25 12:35 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 12:35 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 12:35 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-25 12:35 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 12:35 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 12:35 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-25 12:35 userdata -> /dev/block/mmcblk0p9
Let me know if you still have questions .
@demkantor: This is the output i get for all those commands:
Code:
[email protected]:/ $ su
su
[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
/[email protected] /system ext4 ro,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_ro /system/secro ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /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=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:6 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0
702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3763200 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 56416 mmcblk0p6
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 30760960 mmcblk1
179 97 30756864 mmcblk1p1
[email protected]:/ # ls -l /dev/block
ls -l /dev/block
brw------- root root 7, 0 2013-07-25 10:36 loop0
brw------- root root 7, 1 2013-07-25 10:36 loop1
brw------- root root 7, 2 2013-07-25 10:36 loop2
brw------- root root 7, 3 2013-07-25 10:36 loop3
brw------- root root 7, 4 2013-07-25 10:36 loop4
brw------- root root 7, 5 2013-07-25 10:36 loop5
brw------- root root 7, 6 2013-07-25 10:36 loop6
brw------- root root 7, 7 2013-07-25 10:36 loop7
brw-rw---- root system 179, 0 2013-07-25 10:36 mmcblk0
brw------- root root 179, 32 2013-07-25 10:36 mmcblk0boot0
brw------- root root 179, 64 2013-07-25 10:36 mmcblk0boot1
brw------- root root 179, 1 2013-07-25 10:36 mmcblk0p1
brw------- root root 179, 2 2013-07-25 10:36 mmcblk0p2
brw------- root root 179, 3 2013-07-25 10:36 mmcblk0p3
brw------- root root 179, 4 2013-07-25 10:36 mmcblk0p4
brw------- root root 179, 5 2013-07-25 10:36 mmcblk0p5
brw------- root root 179, 6 2013-07-25 10:36 mmcblk0p6
brw------- root root 179, 96 2013-07-25 10:36 mmcblk1
brw------- root root 179, 97 2013-07-25 10:36 mmcblk1p1
drwxr-xr-x root root 2013-07-25 10:36 platform
drwx------ root root 2013-07-25 10:36 vold
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 236M 56K 236M 4096
/mnt/asec 236M 0K 236M 4096
/mnt/obb 236M 0K 236M 4096
/system 504M 330M 173M 4096
/system/secro 4M 4M 0K 4096
/data 2G 940M 1G 4096
/cache 504M 9M 494M 4096
/storage/sdcard0 29G 12G 16G 32768
/mnt/secure/asec 29G 12G 16G 32768
/storage/sdcard1 55M 24K 54M 4096
[email protected]:/ # busybox df -hm
busybox df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 236.8M 56.0K 236.7M 0% /dev
tmpfs 236.8M 0 236.8M 0% /mnt/asec
tmpfs 236.8M 0 236.8M 0% /mnt/obb
/[email protected] 504.4M 330.9M 173.5M 66% /system
/[email protected]_ro 4.9M 4.9M 0 100% /system/secro
/[email protected] 2.5G 940.0M 1.5G 37% /data
/[email protected] 504.4M 9.6M 494.8M 2% /cache
/dev/block/vold/179:97
29.3G 12.8G 16.5G 44% /storage/sdcard0
/dev/block/vold/179:97
29.3G 12.8G 16.5G 44% /mnt/secure/asec
/dev/block/vold/179:6
55.0M 24.0K 55.0M 0% /storage/sdcard1
[email protected]:/ #
As you can see no mapping shown..
@shimp208: I tried that and this is what i got as output:
Code:
[email protected]:/dev/block/platform # ls
ls
mtk-sd.0
mtk-sd.1
[email protected]:/dev/block/platform # ls -l
ls -l
drwxr-xr-x root root 2013-07-25 10:36 mtk-sd.0
drwxr-xr-x root root 2013-07-25 10:36 mtk-sd.1
[email protected]:/dev/block/platform # ls -l mtk-sd.0
ls -l mtk-sd.0
drwxr-xr-x root root 2013-07-25 10:36 by-num
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk0p6 -> /dev/block/mmcblk0p6
[email protected]:/dev/block/platform # ls -l mtk-sd.1
ls -l mtk-sd.1
drwxr-xr-x root root 2013-07-25 10:36 by-num
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2013-07-25 10:36 mmcblk1p1 -> /dev/block/mmcblk1p1
So as you can see, still not showing the directory name mapping, like which one is system and which one is data etc..
Instead of mapping the mount point directory with dev block it shows some
/[email protected]
/[email protected]_ro
/[email protected]
/[email protected]
This time i ran those commands with ADB..
ibshar said:
So as you can see, still not showing the directory name mapping, like which one is system and which one is data etc..
Instead of mapping the mount point directory with dev block it shows some
/[email protected]
/[email protected]_ro
/[email protected]
/[email protected]
This time i ran those commands with ADB..
Click to expand...
Click to collapse
Try running these commands to get the output:
Code:
ls - l /dev/block/platform/mtk-sd.0/by-name
Or cd into the mtk-sd.0 then:
Code:
ls -l
I think you meant cd into by-num folder, coz there is no folder named by-name. So here is the output:
Code:
[email protected]:/dev/block/platform/mtk-sd.0/by-num $ ls -l
ls -l
lrwxrwxrwx root root 2013-07-25 10:36 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 10:36 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 10:36 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 10:36 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 10:36 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 10:36 p6 -> /dev/block/mmcblk0p6
ok, i think i found most of it, listing the files in root directory showed that they have made some symlinks and that actually maps up with teh mount command output.
ls -l /
Code:
[email protected] -> /dev/block/mmcblk0p3
[email protected] -> /dev/block/mmcblk0p4
[email protected] -> /dev/block/mmcblk0p1
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2
[email protected] -> /dev/block/mmcblk0p5
etc -> /system/etc
thus mapping it with the output of mount command gives:
Code:
em[email protected] -> /dev/block/mmcblk0p3 -> /system
[email protected] -> /dev/block/mmcblk0p4 -> /cache
[email protected] -> /dev/block/mmcblk0p1 ->
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2 -> /system/secro
[email protected] -> /dev/block/mmcblk0p5 -> /data
So now i know about the system, data and cache partitions mapping.. Just need to know about the boot and recovery mapping, also how to get the ramdisk image?
ibshar said:
ok, i think i found most of it, listing the files in root directory showed that they have made some symlinks and that actually maps up with teh mount command output.
ls -l /
Code:
[email protected] -> /dev/block/mmcblk0p3
[email protected] -> /dev/block/mmcblk0p4
[email protected] -> /dev/block/mmcblk0p1
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2
[email protected] -> /dev/block/mmcblk0p5
etc -> /system/etc
thus mapping it with the output of mount command gives:
Code:
[email protected] -> /dev/block/mmcblk0p3 -> /system
[email protected] -> /dev/block/mmcblk0p4 -> /cache
[email protected] -> /dev/block/mmcblk0p1 ->
[email protected] -> /dev/block/mmcblk0p6
[email protected]_ro -> /dev/block/mmcblk0p2 -> /system/secro
[email protected] -> /dev/block/mmcblk0p5 -> /data
So now i know about the system, data and cache partitions mapping.. Just need to know about the boot and recovery mapping, also how to get the ramdisk image?
Click to expand...
Click to collapse
From looking at your devices partition layout from what I can tell I'm guessing mmcblk0boot0 and mmcblk0boot1 are the boot partition blocks and that mmcblk0p2 is your recovery partition if you post the images for those files I can take a look at them for you if you would like to better determine which one truly boot and which is one is truly recovery. Also you can get the ramdisk by extracting it from the boot.img file using a tool such as this one.
shimp208 said:
From looking at your devices partition layout from what I can tell I'm guessing mmcblk0boot0 and mmcblk0boot1 are the boot partition blocks and that mmcblk0p2 is your recovery partition if you post the images for those files I can take a look at them for you if you would like to better determine which one truly boot and which is one is truly recovery. Also you can get the ramdisk by extracting it from the boot.img file using a tool such as this one.
Click to expand...
Click to collapse
Hi thanks for the help.. I have extracted those partitions and uploaded them, please have a look and let me know if they are correct.. http://d-h.st/24I
ibshar said:
Hi thanks for the help.. I have extracted those partitions and uploaded them, please have a look and let me know if they are correct.. http://d-h.st/24I
Click to expand...
Click to collapse
After taking a look at the partition images it seems that your device is using an unconventional partition setup as I was not able to successfully unpack any of the images. Judging from the size of the partitions however the boot partitions you provided do seem to be boot partitions and the recovery partition does seem to be the recovery partition. Unfortunately I can't verify this further unfortunately because of the unconventional partition layout.
shimp208 said:
After taking a look at the partition images it seems that your device is using an unconventional partition setup as I was not able to successfully unpack any of the images. Judging from the size of the partitions however the boot partitions you provided do seem to be boot partitions and the recovery partition does seem to be the recovery partition. Unfortunately I can't verify this further unfortunately because of the unconventional partition layout.
Click to expand...
Click to collapse
Never mind, thanks for the help..
need mount point to setup kitchen.
@ibshar
Sir can you please tell me the mount point for Micromax A110. i want to setup android kitchen.
if possible can you upload the file need to placed in the edify_defs folder of the android kitchen.
Thanks in advance...
subhashdas said:
@ibshar
Sir can you please tell me the mount point for Micromax A110. i want to setup android kitchen.
if possible can you upload the file need to placed in the edify_defs folder of the android kitchen.
Thanks in advance...
Click to expand...
Click to collapse
Sorry man but I don't use that file in the kitchen. I just edit the mount points manually.. The main partitions are
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p7", "/cache");
shimp208 said:
To find out the rest of the mount points and block partition layouts from either terminal or adb shell run the following commands (Make sure to run the commands as root):
First:
Code:
cd /dev/block/platform
Next type:
Code:
ls
And you should see a platform name for example on my Nexus 10 it's dw_mmc.0 cd into the platform name directory (For example):
Code:
cd dw_mmc.0
Then after you have done that cd into the by-name directory:
Code:
cd by-name
And finally once in the by-name directory run the command:
Code:
ls -l
Which should produce an output similar to the following giving you a complete list of mount points and partition block layout:
Code:
lrwxrwxrwx root root 2013-07-25 12:35 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-25 12:35 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-25 12:35 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-25 12:35 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-25 12:35 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-25 12:35 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-25 12:35 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-25 12:35 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-25 12:35 userdata -> /dev/block/mmcblk0p9
Let me know if you still have questions .
Click to expand...
Click to collapse
WHAT THE F*** DUDE!!! After searching all over the Internet, Google, XDA for almost a day... I've finally found the answer to my question!!!

[Q] Request for rooting/modding orbsmart soundpad400 rk3028a

Hi,
I tried all root methods on the net but nothing worked.
Now I tried to add the su binary and the other files how it is described on the rockchipfirmware page.
But it didn't work either. Than I changed the boot.img to get write permission on the /system partition.
The permissions are now VERY unsafe, but nothing is working.
Info:
ro.build.description=rk3028a-user 4.4.4 KTU84P user.lucid.20141014.100831 release-keys
ro.com.google.gmsversion=4.4.4_r4
ro.product.version=1.0.3
Code:
mount:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 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/mtd/by-name/system /system ext4 rw,seclabel,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/metadata /metadata ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.maxmpz.audioplayer.unlock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/system:
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ./
drwxr-x---+ 4 root root 4096 Mai 24 19:52 ../
drwxrwxrwx. 2 root root 4096 Mai 24 00:58 app/
drwxrwxrwx. 3 root 2000 4096 Mai 24 20:18 bin/
-rw-r--r--. 1 root root 3783 Dez 1 03:46 build.prop
drwxr-xr-x. 10 root root 4096 Dez 1 04:03 etc/
drwxr-xr-x. 2 root root 4096 Sep 30 2014 fonts/
drwxr-xr-x. 3 root root 4096 Sep 30 2014 framework/
drwxr-xr-x. 8 root root 8192 Dez 1 03:41 lib/
drwx------. 2 root root 4096 Jan 1 1970 lost+found/
drwxr-xr-x. 3 root root 4096 Dez 1 04:07 media/
drwxr-xr-x. 2 root root 4096 Okt 14 2014 preinstall/
drwxr-xr-x. 2 root root 4096 Okt 10 2014 priv-app/
drwxr-xr-x. 3 root root 4096 Sep 30 2014 tts/
drwxr-xr-x. 8 root root 4096 Sep 30 2014 usr/
drwxr-xr-x. 5 root 2000 4096 Sep 30 2014 vendor/
drwxrwxrwx. 2 root 2000 4096 Mai 23 23:28 xbin/
/system/bin(shorted)
drwxrwxrwx. 3 root 2000 4096 Mai 24 20:18 ./
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ../
-rwsrwsrwt. 1 root 2000 1062992 Mai 24 20:18 busybox*
-rwsrwsrwt 1 root 2000 83 Mai 24 00:17 remount.sh* (self written script to remount /system in rw mode...did not work)
-rwsrwsrwt 1 root 2000 91980 Mai 24 20:18 su*
/system/xbin
drwxrwxrwx. 2 root 2000 4096 Mai 23 23:28 ./
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ../
-rwsr-sr-x 1 root root 1062992 Mai 23 22:07 busybox*
-rwxr-xr-x 1 root root 104800 Mai 23 23:28 daemonsu*
-rwxr-xr-x. 1 root 2000 59748 Sep 30 2014 dexdump*
-rwxr-xr-x. 1 root 2000 9620 Sep 30 2014 io*
-rwsr-sr-x 1 root root 104800 Mai 23 23:27 su*
Do I have to do something else to get root access?
Thanks
Chrno219

[Q] Copying /userdata to sd or PC

I would like to copy a block that contains userdata to SD or a PC.
The author of undelete suggested to use:
adb shell su cat /dev/block/platform/msm_sdcc.1/by-name/userdata > /home/data_image.dat
I connected my phone to a PC and wrote in powercmd:
adb shell
su
cat /dev/block/mmcblk1p1 > /home/data_image.dat
sh: can't create /home/data_image.dat: No such file or directory
What am I doing wrong?
The second question is how to find out what block contains userdata? I just guessed it might be in mmcblk1p1.
When I write "mount" I get:
mount
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/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /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=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.outfit7.talkingtom2free-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.skype.raider-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.VAMflax.ChopperMike-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
I tried going into this dir and ls -al it:
[email protected]:/dev/block/platform # ls -al
ls -al
drwxr-xr-x root root 2015-07-08 11:57 mtk-msdc.1
[email protected]:/dev/block/platform/mtk-msdc.1 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
For some reason mtk-msdc.0 is not visible via ls -al!? But I can cd to it:
[email protected]:/dev/block/platform/mtk-msdc.0 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk0p6 -> /dev/block/mmcblk0p6
So, according to https://blog.avast.com/2014/07/09/android-foreniscs-pt-2-how-we-recovered-erased-data/ that uses "mount" to discover the block for userdata, my userdata is located at /[email protected] But I'm not sure how can I access this directory.
Another thing I don't understand:
[email protected]:/dev/block/platform/mtk-msdc.1 $ ls -al
ls -al
drwxr-xr-x root root 2015-07-08 11:57 by-num
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
[email protected]:/dev/block/platform/mtk-msdc.1 $ su
su
[email protected]:/dev/block/platform/mtk-msdc.1 # ls -al
ls -al
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-07-08 11:57 mmcblk1p1 -> /dev/block/mmcblk1p1
[email protected]:/dev/block/platform/mtk-msdc.1 #
As you can see, my phone ACER Z130 uses "by-num" instead of "by-name" for some reason.
I also wonder why after su I cannot see this dir in ls -l.
Also, some more tries:
D:\Program Files\PowerCmd>adb shell su cat /dev/block/mmcblk1p1 > /home/data.img
The system cannot find the path specified.
D:\Program Files\PowerCmd>adb shell su cat /dev/block/mmcblk1p1 > /data.img
sh: /dev/block/mmcblk1p1: can't execute: Permission denied
So, after reading for hours about how to do that, I'm still stuck.
Also, note, that it seems that on my phone internal mem and sdcard might be reversed in order. At least File Manager shows that sdcard0 has the content of the sd, and sdcard1 has the content of internal memory.
Ok, I did:
2|[email protected]:/ # ls -al
lrwxrwxrwx root root 1970-01-01 07:00 [email protected] -> /dev/block/mmcblk0p6
Ok, found that userdata.
cat /proc/partitions
179 6 2585728 mmcblk0p6
df
/dev 236M 52K 236M 4096
/mnt/secure 236M 0K 236M 4096
/mnt/asec 236M 0K 236M 4096
/mnt/obb 236M 0K 236M 4096
/system 756M 632M 124M 4096
/data 2G 1G 488M 4096
/cache 251M 4M 246M 4096
/protect_f 8M 4M 4M 4096
/protect_s 8M 4M 4M 4096
/storage/sdcard1 2G 1G 438M 4096
/storage/sdcard0 3G 3G 539M 32768
And:
Filesystem volume name: <none>
Last mounted on: /data
Filesystem UUID: 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 163840
Block count: 646176
Reserved block count: 0
Free blocks: 115667
Free inodes: 157106
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 95
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Wed Jul 8 11:57:16 2015
Last write time: Wed Jul 8 11:57:16 2015
Mount count: 1
Maximum mount count: -1
Last checked: Wed Jul 8 11:57:10 2015
Check interval: 0 (<none>)
Lifetime writes: 95 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 131321
Default directory hash: tea
Journal backup: inode blocks
So, I assume the size of the block is about 2.5GB?
Ok, so how can I copy it now to my PC (preferable) or to SD?
dd if=/dev/block/mmcblk0p6 bs=4194304 of=/storage/sdcard0/data.img
adb pull /storage/sdcard0/data.img /Users/????/Desktop/data.img
or try this (i dont know if it will work)
adb shell su -c 'cat /dev/block/mmcblk0p6' > /Users/????/Desktop/data.img
if that doesn't work try this
adb shell 'su -c 'cat /dev/block/mmcblk0p6'' > /Users/????/Desktop/data.img
you need admin rights to write data.img in C:\ , so put your desktop folder.
Ok,
I managed to do that. Now I have the image and I would like to recover the deleted/corrupted contacts2.db file. Any suggestions how to do that?
Blackion said:
Ok,
I managed to do that. Now I have the image and I would like to recover the deleted/corrupted contacts2.db file. Any suggestions how to do that?
Click to expand...
Click to collapse
Boot into linux and mount the image,
Code:
[email protected] ~ # mount /path/to/data.img /mnt
[email protected] ~ # cd /mnt
[email protected] /mnt # nautilus .
Also please quote me or mention me if you're replying to me, I don't get a notification if you don't do it.

[solved][i9100][5.1.1][CM12.1] Read only permission on extSdCard formatted with Ext4

Hello!
I have put a MicroSD card in the device that I formatted with Ext4 with my PC in advance.
On the MicroSD card I copied > 10GB of data.
The MicroSD is mounted correctly in /storage/sdcard1:
Code:
[email protected]:~$ adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,seclabel,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /preload ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:9 /mnt/secure/asec ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:9 /mnt/media_rw/sdcard0/.android_secure ext4 rw,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Checking the user and group permissions they are equal for /storage/sdcard0 and /storage/sdcard1:
Code:
[email protected]:~$ adb shell ls -l /storage
drwxrwx--x root sdcard_r 2015-08-08 14:33 sdcard0
drwxrwx--x root sdcard_r 2015-08-06 20:27 sdcard1
drwxrwx--- root root 2015-08-08 11:36 usbdisk0
This is also true for any file / directory stored in /storage/sdcard1:
Code:
[email protected]:~$ adb shell ls -l /storage/sdcard1
drwxrwx--x root sdcard_r 2015-03-28 16:11 Android
drwxrwx--- root sdcard_r 2015-08-05 17:41 DCIM
drwxrwx--- root sdcard_r 2015-08-06 02:13 TWRP
drwxrwx--- root sdcard_r 2015-08-05 10:34 TitaniumBackup
drwxrwx--- root sdcard_r 2015-03-28 16:11 audio
drwxrwx--- root sdcard_r 2015-08-04 17:10 backup
drwxrwx--- root sdcard_r 2015-03-28 16:12 bilder
drwxrwx--- root sdcard_r 2015-04-23 16:40 brouter
drwxrwx--- root sdcard_r 2015-05-21 14:43 clockworkmod
drwxrwx--- root sdcard_r 2015-03-28 16:17 data
drwxrwx--- root sdcard_r 2015-03-28 16:19 documents
drwxrwx--- root sdcard_r 2015-08-05 22:55 download
drwxrwx--- root sdcard_r 2015-05-31 22:02 keepass
drwxrwx--- root sdcard_r 2015-08-05 22:16 lost+found
drwxrwx--- root sdcard_r 2015-03-28 16:27 musik
drwxrwx--- root sdcard_r 2015-08-03 20:49 oruxmaps
drwxrwx--- root sdcard_r 2015-03-28 16:29 video
-rw-rw---- root sdcard_r 307873 2015-08-08 16:20 xposed-uninstaller-arm.zip
-rw-rw---- root sdcard_r 3540968 2015-08-08 16:20 xposed-v69-sdk22-arm-by-romracer-20150804.zip
However, I cannot write any file to /storage/sdcard1/<subdirectory>:
Code:
[email protected]:/storage/sdcard1 $ cp -v xposed-* backup/
cp: backup/xposed-uninstaller-arm.zip: Permission denied
cp: backup/xposed-v69-sdk22-arm-by-romracer-20150804.zip: Permission denied
Question:
Why is any subdirecty in /storage/sdcard1 with read-only permission?
THX
So, how do U solve the problem?

Porting CWM to Goclever Quantum 500 - black screen

Hey.
I would like to port CWM to Goclever Quantum 500
I use the official documentation from cyanogenmod website
Compilation goes flawlessly.
Code:
Install: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery/root/sbin/recovery
----- Making recovery ramdisk ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat '/home/mazur/android/system/out/target/product/java_gfive_wg5002g/root/init.recovery.*.rc': No such file or directory
----- Making uncompressed recovery ramdisk ------
----- Making compressed recovery ramdisk ------
----- Making recovery image ------
+/home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img maxsize=34197504 blocksize=135168 total=8536064 reserve=405504
Made recovery image: /home/mazur/android/system/out/target/product/java_gfive_wg5002g/recovery.img
#### make completed successfully (32:32 (mm:ss)) ####
But after flashing (flash goes flawlessly too - I tried flashify and fastboo btw) and trying entering the recovery I see only a black screen and nothing more.
Before flashing CWM I have generated stock recovery using flashify. Reflasing stock recovery works perfectly.
I have edited recovery.fstab based on recovery stock
recovery.fstab
Code:
# mount point fstype device option
/dev/block/platform/sdhci.0/mmcblk1p1 /sdcard vfat defaults wait
/dev/block/platform/sdhci.1/by-name/sdcard /sdcard0 vfat defaults wait
/dev/block/platform/sdhci.1/by-name/system /system ext4 rw wait
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw wait,length=-16384
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw wait
/dev/block/platform/sdhci.1/by-name/misc /misc emmc rw wait
/dev/block/platform/sdhci.1/by-name/boot /boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/recovery /recovery emmc rw wait
/dev/block/platform/sdhci.1/by-name/u-boot /u-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/dt-blob /dt-blob emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-boot /cp-boot emmc rw wait
/dev/block/platform/sdhci.1/by-name/cp-image /cp-image emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-dram /dsp-dram emmc rw wait
/dev/block/platform/sdhci.1/by-name/dsp-pram /dsp-pram emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-ind /sys-parm-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-ind /parm-spml-ind emmc rw wait
/dev/block/platform/sdhci.1/by-name/ubootlogo /ubootlogo emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi /abi emmc rw wait
/dev/block/platform/sdhci.1/by-name/abi-sec /abi-sec emmc rw wait
/dev/block/platform/sdhci.1/by-name/hwconf /hwconf emmc rw wait
/dev/block/platform/sdhci.1/by-name/loader /loader emmc rw wait
/dev/block/platform/sdhci.1/by-name/parm-spml-dep /parm-spml-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/sys-parm-dep /sys-parm-dep emmc rw wait
/dev/block/platform/sdhci.1/by-name/umts-cal /umts-cal emmc rw wait
BoardConfig.mk generated by mkvendor.sh
[..]
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE :=891289600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1614807040
BOARD_FLASH_BLOCK_SIZE := 131072
[..]
some info from adb shell:
Code:
[email protected]_gfive_wg5002g:/ # df
Filesystem Size Used Free Blksize
/dev 479.0M 128.0K 478.8M 4096
/sys/fs/cgroup 479.0M 12.0K 479.0M 4096
/mnt/secure 479.0M 0.0K 479.0M 4096
/mnt/asec 479.0M 0.0K 479.0M 4096
/mnt/asec/com.koushikdutta.rommanager-1 5.0M 3.6M 1.4M 4096
/mnt/asec/zip.me-1 6.1M 4.2M 1.9M 4096
/mnt/asec/me.kuder.diskinfo-1 3.0M 1.1M 1.9M 4096
/mnt/asec/com.cgollner.flashify-2 17.2M 14.1M 3.0M 4096
/mnt/asec/org.xbmc.kore-1 4.0M 2.9M 1.1M 4096
/mnt/asec/com.cpuid.cpu_z-1 4.0M 2.4M 1.6M 4096
/mnt/obb 479.0M 0.0K 479.0M 4096
/mnt/media_rw/sdcard0 1022.0M 686.0M 336.0M 4096
/mnt/media_rw/sdcard1 12.7G 674.4M 12.0G 4096
/storage/emulated 479.0M 0.0K 479.0M 4096
/storage/sdcard0 1022.0M 686.0M 336.0M 4096
/storage/sdcard1 12.7G 674.4M 12.0G 4096
/system 823.3M 632.6M 190.7M 4096
/cache 143.6M 232.0K 143.4M 4096
/data 1.5G 1.3G 183.1M 4096
/storage/emulated/legacy 479.0M 0.0K 479.0M 4096
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
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /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/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/zip.me-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/me.kuder.diskinfo-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.cgollner.flashify-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/org.xbmc.kore-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.cpuid.cpu_z-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,size=0k,mode=700,uid=1023,gid=1023 0 0
/dev/block/vold/179:32 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:169 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=0k,mode=751,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/sdhci.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,data=ordered 0 0
/dev/block/platform/sdhci.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
Code:
[email protected]_gfive_wg5002g:/ # ls -la /dev/block/platform/sdhci.1/by-name/
lrwxrwxrwx root root 2013-01-01 01:02 abi -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-01 01:02 abi-sec -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-01-01 01:02 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-01-01 01:02 boot-parm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-01-01 01:02 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2013-01-01 01:02 cp-boot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-01-01 01:02 cp-image -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-01-01 01:02 cp-pod -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-01-01 01:02 custom-cert -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-01-01 01:02 devinfo -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-01-01 01:02 dsp-dram -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-01-01 01:02 dsp-pram -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-01-01 01:02 dt-blob -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-01-01 01:02 hwconf -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-01 01:02 kpanic -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2013-01-01 01:02 loader -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-01-01 01:02 misc -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-01-01 01:02 mobicore -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-01-01 01:02 oeminfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-dep -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-01-01 01:02 parm-spml-ind -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-01-01 01:02 ramdisk-broadcom -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2013-01-01 01:02 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2013-01-01 01:02 sdcard -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-dep -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-01-01 01:02 sys-parm-ind -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-01-01 01:02 system -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2013-01-01 01:02 u-boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-01-01 01:02 u-boot-env -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-01-01 01:02 ubootlogo -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-01-01 01:02 umts-cal -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-01-01 01:02 userdata -> /dev/block/mmcblk0p31
Code:
[email protected]_gfive_wg5002g:/dev/block/platform/sdhci.1/by-name # for x in `ls`;do busybox fdisk -l $x;done
[....]
Disk boot: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Disk boot-parm: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Disk cache: 157 MB, 157286400 bytes
4 heads, 16 sectors/track, 4800 cylinders
Disk cp-boot: 0 MB, 32768 bytes
4 heads, 16 sectors/track, 1 cylinders
Disk loader: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Disk misc: 0 MB, 262144 bytes
4 heads, 16 sectors/track, 8 cylinders
Disk ramdisk-broadcom: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk recovery: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Disk sdcard: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders
Disk system: 891 MB, 891289600 bytes
4 heads, 16 sectors/track, 27200 cylinders
Disk u-boot: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Disk ubootlogo: 5 MB, 5242880 bytes
4 heads, 16 sectors/track, 160 cylinders
Disk userdata: 1614 MB, 1614807040 bytes
4 heads, 16 sectors/track, 49280 cylinders
[..]
my CWM recovery image dropbox.com/s/1r4bkppweenkmxs/recovery.img?dl=0
my Stock recovery: dropbox.com/s/imndi2fg5t9vr54/Stock%20Recovery?dl=0
Sorry for post splitting and weak link. I was unable to send one so long post and links
Can you help me solve this problem?

Categories

Resources