I have no idea if this belongs here, so feel free to move this thread.
I have a Qualcomm MDP MSM8660, which, frankly, I am way too much of a noob to use. I, with the help of someone, finally managed to install gapps and am able to use the market. The problem is, the Market claims that there is no room to install apps, even though the phone says that there is 888MB free. So I presume that the market sees some other partition which is full. If this is the case, how can I make it see the other partition, or alternatively expand the partition. I don't even know how to view the partitions to see if the above theory is correct.
EDIT: I checked using Android System Information, and the Data partition is nearly a Gigabyte. So any suggestions on why the Market thinks that there is no room. When I used ADB to push the gapps to /system there also wasn't any room, so I had to clear some apps. But I believe that's a different partition.
Any ideas?
Thanks
To view the partitions on your device you should run mount through adb shell. Post the output here.
Here it is:
>adb shell mount
rootfs / rootfs ro,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
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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /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
/dev/block/dm-0 /mnt/asec/com.estrongs.android.pop-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
EDIT: Not really related, but I even though this is supposed to be rooted, and through ADB it does seem so , after remount, Superuser says it's not and in Terminal it shows "$" and when I type "su" it says uid 10006 not allowed to su". Any ideas?
Does anyone have any ideas? Also how to symlinks?
Thanks.
Hi! I want backup /efs but its empty. Efs isnt mounted(checked in terminal and adb). Phone is rooted. How i can backup /efs (IMEI etc.) if /efs is empty? Phone isnt missing IMEI (starts 357... same as in box) and phone is working well. i Have tried DD different partitions and mount them on my linux pc, but didint found /efs(nv_data.bin etc) (version PDA/PHONE: S5360XXKJ1)
Code:
/ # mount
rootfs / rootfs ro,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl11 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /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 /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
CWM 5.0.2.7 Touch Recovery
This is a port of CWM touch recovery modded by Team UtterChaos.
Installation is same as the 5.0.2.6 recovery.
Changelog:
3)Changed icons and layout.
2)Changed icon layout to vertical alignment as recovery text merges with icons.
1)Initial release
Credit:
All credit goes to koush and members of Team UtterChaos
Note:Im not sure if this will work for ITE devices but you can try.
good to see any new tool for our veiwpad thx hero, and it's funny to see ics icon on recovery, hehe.
My Vpad7 with ITE hardware was running 5.0.2.6 so I used Terminal to flash this, it rebooted but I can't get into the Advanced submenu and at least one other submenu - Go Back doesn't work for me either. The nice icon/graphic just sitting there in the center screen, so I've reverted back to older one as I need to use its feature to format/setup ext3 and/or ext4.
Anyone else having luck & success with this, it could be just me - tried it twice.
Would this work for viewpad 7e?
Sent from my LG-P500 using xda premium
hellodzulz said:
Would this work for viewpad 7e?
Click to expand...
Click to collapse
No, this is all for the Viewpad 7, not the Viewpad 7e. The 7e is basically a new product and we just need to wait until Viewsonic sells enough of these 170$ tablets to warrant someone elses interest in creating a mod for it.
Not sure how a bounty would work, but I would put in 30$. Once Clockwork Recovery works, then it should be easy for someone else to provide a stock ROM for it that lets Marketplace work better.
elister said:
No, this is all for the Viewpad 7, not the Viewpad 7e. The 7e is basically a new product and we just need to wait until Viewsonic sells enough of these 170$ tablets to warrant someone elses interest in creating a mod for it.
Not sure how a bounty would work, but I would put in 30$. Once Clockwork Recovery works, then it should be easy for someone else to provide a stock ROM for it that lets Marketplace work better.
Click to expand...
Click to collapse
I could help you with that.
just pm me the following stuff:
Boot.img
Partition table
mb-14 said:
I could help you with that.
just pm me the following stuff:
Boot.img
Partition table
Click to expand...
Click to collapse
Im pretty sure I would need ADB Shell in order to do that, but ADB Shell cannot find the 7e as a device.
elister said:
Im pretty sure I would need ADB Shell in order to do that, but ADB Shell cannot find the 7e as a device.
Click to expand...
Click to collapse
ADB shell is not necessary.Just download a terminal emulator from the market.
mb-14 said:
ADB shell is not necessary.Just download a terminal emulator from the market.
Click to expand...
Click to collapse
What commands would I need to execute to create the image and display the partitions?
elister said:
What commands would I need to execute to create the image and display the partitions?
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
mb-14 said:
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Click to expand...
Click to collapse
Using the terminal emulator version, I got the romdump installed, but the folder it created contained no files.
-----------------------------------------------------------
#/system/bin/romdump
Android ROM dumper v0.72b
(c)2010 Sebastian404
Device : ViewPad7e 2.3.1 GINGERBREAD 2011.11.01
[2] Segmentation fault /system/bin/romdump
[1] Segmentation fault /data/local/install
#
-----------------------------------------------------------
Yes I remember to toggle wifi on, then off. I'll try a few more times when im not drunk.
elister said:
Using the terminal emulator version, I got the romdump installed, but the folder it created contained no files.
-----------------------------------------------------------
#/system/bin/romdump
Android ROM dumper v0.72b
(c)2010 Sebastian404
Device : ViewPad7e 2.3.1 GINGERBREAD 2011.11.01
[2] Segmentation fault /system/bin/romdump
[1] Segmentation fault /data/local/install
#
-----------------------------------------------------------
Yes I remember to toggle wifi on, then off. I'll try a few more times when im not drunk.
Click to expand...
Click to collapse
Try the alternative method given in the link.
mb-14 said:
Try the alternative method given in the link.
Click to expand...
Click to collapse
You mean ADB Shell? Nah, that never worked. Could never get the USB drivers from the SDK to work. Shows up in Unknown Devices as ViewPad 7e, unless theres some device drivers im not aware of. Searching for them brings up countless Vewsonic 7e Monitor drivers, not tablet ones.
No problem getting my android phone rooted with ICS, but this tablet is just too new I guess.
elister said:
You mean ADB Shell? Nah, that never worked. Could never get the USB drivers from the SDK to work. Shows up in Unknown Devices as ViewPad 7e, unless theres some device drivers im not aware of. Searching for them brings up countless Vewsonic 7e Monitor drivers, not tablet ones.
No problem getting my android phone rooted with ICS, but this tablet is just too new I guess.
Click to expand...
Click to collapse
Adb shell is not necessary.The commands will also work on your terminal emulator on the phone.Skip the first instruction "adb shell"
I was unable to get the romdump to work, so I tried looking at the mounts (seen below). I am not sure if it helps, but if there is something I can do, please let me know. I'd love to get a nandroid backup of the the 7e
Thanks.
rootfs / rootfs ro,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
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
/dev/block/mmcblk0p2 /system ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
mmarsman said:
I was unable to get the romdump to work, so I tried looking at the mounts (seen below). I am not sure if it helps, but if there is something I can do, please let me know. I'd love to get a nandroid backup of the the 7e
Thanks.
rootfs / rootfs ro,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
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
/dev/block/mmcblk0p2 /system ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Click to expand...
Click to collapse
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
mb-14 said:
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
Click to expand...
Click to collapse
It doesn't show anything, just the headers:
dev: size erasesize name
is there another option instead of mtd that it could be?
---------- Post added at 03:28 PM ---------- Previous post was at 02:32 PM ----------
mb-14 said:
I need the partition names and their sizes.This is not going to help.What command did you run?
Try this from the terminal emulator:
su
cat /proc/mtd
and post me the output
Click to expand...
Click to collapse
I also tried running: cat /proc/partitions
It returned the following:
major minor #blocks name
179 0 3772416 mmcblk0
179 1 2605798 mmcblk0p1
179 2 209901 mmcblk0p2
179 3 525698 mmcblk0p3
179 4 115351 mmcblk0p4
179 8 16186368 mmcblk1
179 9 16185344 mmcblk1p1
Still not right, but I will keep trying
Finally people interested in the ViewPad 7e, I will try to get the partitions info and the img files tonight wish me luck
Viewpad 7e Info
This is going to be a little long, but I have been searching for days and I am not sure where things are going wrong. When I run cat /proc/mtd it will only return the headers. I found another forum posting that had a sequence of commands that my reveal some useful information. Below I am showing the commands and their results. If anyone has a suggestion of where to go from here I'm all ears.
cat proc/mtd
Code:
dev: size erasesize name
cat proc/mounts
Code:
rootfs / rootfs ro,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
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
/dev/block/mmcblk0p2 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
ls /dev/block/mmcblk*
Code:
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
mount
Code:
rootfs / rootfs ro,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
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
/dev/block/mmcblk0p2 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/ViewPad_7e vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/ViewPad_7e/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
df
Code:
Filesystem Size Used Free Blksize
/dev 163M 32K 163M 4096
/mnt/asec 163M 0K 163M 4096
/mnt/obb 163M 0K 163M 4096
/system 198M 171M 26M 1024
/data 503M 130M 373M 4096
/cache 109M 103M 5M 1024
/mnt/ViewPad_7e 2G 100M 2G 4096
/mnt/secure/asec 2G 100M 2G 4096
The 7e seems to have emmc partitions instead of mtd.
Try this:
cat /proc/emmc
hello,
i have two sch-r930 phones. (samsung galaxy s aviators) and through countless forums's and googling i cannot for the life of me find the recovery partitions, among others. even tho i have attempted all possibilities (the ones i found atleast) to find these, i ask others for assistance.
anything needed as far as output's from any commands or binaries can be provided.
help?
Looks like this might do the trick:
https://play.google.com/store/apps/details?id=com.cls.partition
or if you prefer to know how manually, then there might be some helpful info on this thread:
http://forum.xda-developers.com/showthread.php?t=2377989
exhausted that
es0tericcha0s said:
Looks like this might do the trick:
https://play.google.com/store/apps/details?id=com.cls.partition
or if you prefer to know how manually, then there might be some helpful info on this thread:
http://forum.xda-developers.com/showthread.php?t=2377989
Click to expand...
Click to collapse
already attempted those. actually any app with partition in the title ive downloaded from the playstore and tried.
i have tried to ls -l /dev/block/platform and looked for a by-name in either location to no end. i have chekced the last_log from the cache/partition. i have used onandroid, romgen, romdump, flash_image, dump_image, etc to no end.
i need someone who can help me narrow it down by some other means.
is it possible that its wrapped up in with the kernel?
moar
heres my mount results
# mount
mount
rootfs / rootfs ro,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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/radio tmpfs rw,relatime 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/stl10 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/mmcblk0p1 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p4 /fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/
rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/u
id/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
/dev/block/stl7 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
Hi all,
I have a Samsung Galaxy S4 (gt-i9505) on which I have Philz CWM Recovery and have install CyanogenMod 11.
I have two identical phones on which I have done exactly the same procedure (I thought!) to install the new ROM and recovery and one of them is perfectly fine whereas the other one is experiencing the following issue...
Everything has worked fine and the phone functions ok except while I was installing the ROM I found that I couldn't save anything to my external SD card. Now, since the ROM has been installed the external SD card is not accessible and attempting to mount it under the Storage menu says 'mounting ...' in the notification area but then doesn't nothing and the card is not mounted.
I assume I have done something to the permissions or symlinks when in the recovery but can't figure out what I did. I have inspected the file system of both phones via adb and the layout of folders and symlinks looks identical. The fstab.qcom and init.qcom.rc files also look identical.
When running the mount command on the phone with the SD card issue I get the following output:
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/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/lv.mendo.posingapp-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
Any ideas?
thanks
Aaron