Related
Yeah I was testing out Dharam's battery saver rom but when I go to restore data from cwm it says unable to mount stl7 and here is what i get when i do adb shell mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl6 /system rfs ro,nodev,noatime,nodiratime,vfat,log_off,check=no,gi
d/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,g
id/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,
gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl4 /efs 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,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
EDIT: I see that when i go to the mount and storage menu in CWM it says
E: can't mount /dev/block/stl7
(invalid argument)
Error mounting DATA:!
E: can't mount /dev/block/stl7
(invalid argument)
Error mounting DATA:!
I tried reflashing cwm and everything but still nothing :S
Thanks in advance
Galaxy Tab 10.1 GT-P7510 32GB, stock, not yet rooted
kernel: #1 SMP PREEMPT Mon Jun 6 08:59:10 KST 2011
PDA: KF3, phone: KF3; CSC: KF3 (XAB)
Starting down the path to root the phone, I encounter an issue that I haven't seen on the fora.
If I boot to recovery, I get to menu about "reboot system now", "apply update from /sdcard" and so on, but if I pick "apply update from /sdcard" it can't find what I've put in /sdcard. I get an error "E: unknown volume for path [/sdcard]".
While in this recovery state, if I adb shell, do "mount", I see that nothing is mounted on /mnt/sdcard:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p4 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
In normal running state, if I adb shell "mount" I get:
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
debugfs /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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm quite surprised that /mnt/sdcard is not mounted in a mode where it's supposed to be able to do update.zip things from there.
Am I being stupid? (No surprise if that turns out to be the case.)
--bogoid
I am having the exact same issue with my Galaxy Tab 10.1. Anyone help would be greatly appreciated.
Adam
Ditto - have you guys found a fix yet?
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
msm903 said:
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
Click to expand...
Click to collapse
That did the trick! Thank you!
Hey everyone,
This is pretty embarrassing... I successfully ran the following:
Code:
mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
But now I cannot revert back to the original mount point of "/sdcard"
I've even tried umount-ing with the force-flag and still no luck
I'd appreciate any help at all, thanks
It *might* revert when you reboot unless you overwrote something.
Why are you screwing with this anyways?
Thanks for the quick reply.
Rebooting didn't change it.
Edit: Below is fixed, no longer relevant
Except, now I'm noticing I have to root with SuperOneClick each time I reboot to get su access.
The only thing I did after running the mount command, was install BusyBox
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
jasongw said:
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
Click to expand...
Click to collapse
There's an "sdcard" partition. It's whats mounted when you attach your KF to your PC... But no, there's no removable SD Card
Not sure 100% what the correct command to remount the sdcard partition is so can't say much right now.
check under /proc/mounts and also under /proc/emmc (open them as a text file) and paste what it says.
Didn't see a /proc/emmc but here's what I found
Contents of /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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12[B][COLOR="Red"] /mnt/sdcard[/COLOR][/B] 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:12 /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[B][COLOR="Red"] /mnt/sdcard/[/COLOR][/B].android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.angrymobgames.muffinknight3rdparty-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I hope you can solve your problem,good luck
looks like you need to mount /dev/block/vold/179:12 so rerun the command you were doing with that instead.
I installed Astro File Manager, through which I can view the sdcard partition's contents in "/sdcard" as well as "/mnt/sdcard"
I only seem to have issues viewing contents of location "/sdcard" in adb shell.
At this point I'm not too terribly concerned about it. Maybe I'm making a deal out of nothing...
I do appreciate your help though.
And if anyone knows the exact solution, then please speak up
EDIT:
Returns nothing:
Code:
ls /sdcard
Returns contents:
Code:
cd /sdcard
ls
I guess nothing was ever wrong after all.. Now I feel extra-dumb
First I want to thank all the devoted developers here, who all do a great job.
I am a proud owner of a GT-S5360 for 2 days now, and as I am a Sysadmin (although not into linux that much) I had to try to flash my device, of coursse. I am new to this, but I already had the honour to flash a Galaxy Tab at work once wich worked just fine.
But not quite with my GT-S5360.
Here is what I did:
I tried to flash the Jellyblast v3 according to this thread:
http://forum.xda-developers.com/showthread.php?t=1679563
Of course i rooted the divice:
http://www.galaxy4gaming.in/2012/07/root-unroot-samsung-galaxy-y.html
While in CWM trying to wipe data, clear cache and dalvik cache, I got error messages like these:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
as stated already here:
http://forum.xda-developers.com/showthread.php?t=1150917
Thus I upgraded my linux skills and did some adb shell work and installed busybox on my device.
As the above thread is for the HTC Desire I'm now not sure what to make of my results. I don't think its the eMMC chip, thats faulty.
Code:
dmesg | grep mmc0
gave me
Code:
# dmesg | grep mmc0
dmesg | grep mmc0
<6>[ 2.058532] mmc0: SDHCI controller on [bcm_sdhc.1] using ADMA
<4>[ 2.063812] mmc0: mmc_rescan start
<4>[ 2.063842] mmc0: mmc_rescan rescann is out
<4>[ 22.212402] mmc0: mmc_rescan start
<6>[ 22.308227] mmc0: new high speed SDIO card at address 0001
<4>[ 22.815917] mmc0: mmc_rescan rescann is out
I googled the results, but with no result, at least none that i could understand.
It semms that the SD Card is working fine, as I can put all the .zip files and other stuff onto it, but the /cache and /data folders are inaccessible.
Is it possible, that the system is somehow secured?
I really did some deep reading in the forum but now I'm kinda stuck.
If anyone can help me, it would be really, really appreciated.
kind regards
Frank
here are some more adb shell results.
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=cp
437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp
437 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,ioch
arset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
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=cp
437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp
437 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,ioch
arset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
# df
df
Filesystem Size Used Free Blksize
/dev 144M 52K 144M 4096
/mnt/asec 144M 0K 144M 4096
/mnt/obb 144M 0K 144M 4096
/system 221M 214M 7M 4096
/cache 35M 20K 35M 4096
/data 189M 44M 145M 4096
/mnt/sdcard 1G 224M 1G 32768
/mnt/secure/asec 1G 224M 1G 32768
which cwm u using?
try to mount system/data
CALIBAN666 said:
which cwm u using?
try to mount system/data
Click to expand...
Click to collapse
I downloaded it via the link in this thrad, as told...
http://forum.xda-developers.com/showpost.php?p=26703127&postcount=8
....
error mounting /data
do not have option mount /system
frank_77 said:
I downloaded it via the link in this thrad, as told...
http://forum.xda-developers.com/showpost.php?p=26703127&postcount=8
....
error mounting /data
do not have option mount /system
Click to expand...
Click to collapse
use the temporary CWM by madteam
or get a permanent CWM via kernels like savie, merruk, white
deathnotice01 said:
use the temporary CWM by madteam
or get a permanent CWM via kernels like savie, merruk, white
Click to expand...
Click to collapse
thank you for your reply deathnotice and caliban.
it seems to work
so it was the CWM.
many thanks for your help.
kind regards
Frank
Hello, since yesterday I can't write anything om my external memory-card (sdcard0) anymore. No idea what caused this
CM: nightly 24.11.2014 (happens also on older builds until 16.11.)
Mounts (recorded with the mount command via terminal):
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
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,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data_root ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/ginlemon.flowerpro-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:27 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/block/vold/179:27 /mnt/secure/asec ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-2 /mnt/asec/com.sonny.lpi.frost2-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
Hmmm - I hope I did provide enough information ...
I'm wondering whether it is possible to unmount /mnt/media_rw/sdcard0 in a terminal and mount it again with read-write enabled?
Not sure how to proceed and a bit anxious about it as well since I don't know enough about Android despite working with Linux since 20 years
I guess your filesystem is corrupted. Please post dmesg logs.
Here's the dmesg.log -> https://gist.github.com/wimstefan/7af22e19b6ff408a7c22
Thanks for looking into it!
If needed I also can provide the logcat I took this afternoon ...
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
m11kkaa said:
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
Click to expand...
Click to collapse
Oh I see
Well running the command above seems not to do that much:
Code:
# e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/msm_sdcc.1/by-name/system: 1944/32768 files (0.5% non-contiguous), 106443/131072 blocks
Same happens with system1 ... but that's not where the errors in dmesg are listed or am I completely wrong now? I see some fs errors passing dmesg regarding device mmcblk0p27 which is /dev/block/platform/msm_sdcc.1/by-name/storage. Running the e2fsck command on that device was a completely different story! A lot of errors and corrections ... the filesystem was modified at the end and after a reboot it is mounted writable again!
So THANK YOU VERY MUCH for pushing me in the right direction !!! :highfive: :victory:
Hopefully everything is alright again and I can continue to enjoy my MI2S
yeah sorry I meant storage. stupid copy&paste errors