[Q] Q - no sdcard is mounted - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi.
I had rooted (CF-Root-XW_XEN_JS5-v1.3) galaxy i9000 and I updated it with CF-Root-XW_XEE_JVB-v3.1-CWM3RFS. Odin said - successful, but phone after that never boot up successfully, just showed 'Galaxy S ...' on the screen.
Via recovery, using adb shell is see now:
$ busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 169.5M 0 169.5M 0% /dev
nodev 169.5M 8.0K 169.5M 0% /tmp
df: /mnt/.lfs: Function not implemented
tmpfs 169.5M 0 169.5M 0% /mnt/asec
/dev/block/stl9 275.8M 274.2M 1.6M 99% /system
/dev/block/stl3 5.9M 5.0M 933.0K 85% /efs
/dev/block/stl11 30.1M 4.0M 26.1M 13% /cache
Before update it showed:
tmpfs 169.5M 0 169.5M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 169.5M 0 169.5M 0% /mnt/asec
/dev/block/stl9 275.8M 274.2M 1.7M 99% /system
/dev/block/mmcblk0p2 1.9G 354.3M 1.5G 18% /data
/dev/block/stl10 127.2M 12.4M 114.8M 10% /dbdata
/dev/block/stl11 30.1M 4.0M 26.1M 13% /cache
/dev/block/stl3 5.9M 5.0M 935.0K 85% /efs
/dev/block/vold/179:1 13.4G 4.0G 9.4G 30% /mnt/sdcard
Any suggestions, how could I get my sdcard and data volumes again mounted? Somehow via adb mount or should I use Odin with repartition?

Related

[Q] Mount /system in R/W

Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
stupid question, but I have to ask: are you rooted?
o0beaner said:
Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
Click to expand...
Click to collapse
Try backing all the way out of the folder by pressing the (...) button at the top. Keep pressing that until you are at the root folder (it won't be there anymore). Now press the r/w button at the top. It should change, and will stay changed once you go back into the other folders.
Sorry, it was early, and my brain wasn't good for specifics. I am rooted, running SRE 1.2.
Root is mounted R/W, but /system will not change state. Is there anything I can try from the terminal?
Same problem here on my wife's Captivate. I used SRE 1.2.1a and noticed that I was still seeing ads. So I tried installing Adfree and updating the host file and ran into the same mounting error.
On my own Captivate, I had used 1-Click root before SRE came out and no problems updating there.
same here no ADFREE in SREv2b7. I tried R/W on Root explorer and even trying to change permissions on sys,system, data/data, and still get same error as you guys re-mount /system.
Let's see where /system is mounted:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
[/COLOR]/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
Thanx but that didnt work this are my setting
C:\AndroidSDK\tools>adb shell
$ mount
mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p4 /data ext4 rw,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
IM STILL GETTING failed to remount system partition read-only
I can't update AdFree either.
shilob said:
Let's see where /system is mounted:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
[/COLOR]/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
Click to expand...
Click to collapse
Didn't work for me either--still got the "failed to mount read-only file system" or something like that. Also, when I tried the "-o remount,ro" adb said device or resource busy. I'm pretty sure this has been discussed in the SRE thread, but i really, really, want adree to work

need help with app2sd badly.. pls

i think i managed to get the app2sd installed.
however i'm unable to confirm if its working. it appears my /system/sd is there but when i went to /data/app and did a pwd
it appears the prompt still return /data/app instead of /system/sd/app
anyone know what i did wrong and what i can do to address the symbolic link?
Thanks
# ./busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 112.5M 0 112.5M 0% /dev
tmpfs 4.0M 16.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock6 175.6M 146.5M 29.2M 83% /system
/dev/block/mtdblock8 197.1M 58.0M 139.1M 29% /data
/dev/block/mtdblock7 106.0M 3.0M 103.0M 3% /cache
/dev/block/mtdblock5 8.8M 8.4M 328.0K 96% /cdrom
tmpfs 2.0M 24.0K 2.0M 1% /tmp
/dev/block/mtdblock0 1.5M 1.2M 268.0K 83% /pds
/dev/block/mmcblk0p2 984.3M 17.3M 917.0M 2% /system/sd
/dev/block//vold/179:1
13.7G 3.5M 13.7G 0% /sdcard
# cd /data/app
# pwd
/data/app

after i've installed ezgingerbread, problem with MTD

After i've installed ezgingerbread on my G1 (radio 2.22.28.25 SPL 1.33.0013d), I have problem restoring my nandroid backup of Gingerfroyo (Restore the rom, but lost all settings).
If i install Gingerfroyo rom again , I can't download apk larger than 2 MB from market.
How can I solve this problem?
Thanks and excuse me for my english.
ezGingerbread doesn't touch the partitions, it takes the standard layout of the 1.33.0013(d) SPL. I am not sure if GingerFroyo touches the partition map, I've never installed it.
If your market downloads are not working, probably removing the folder ".android_secure" from your /sdcard will help you.
If i delete .android_secure, it recreate again. The market have the same problem.
I can't download .Apk larger than 2 MB from market.
Gingerfroyo don't touch the partitions.
00040000 00020000 misc
00500000 00020000 recovery
00280000 00020000 boot
05b00000 00020000 system
01b00000 00020000 cache
05bc0000 00020000 userdata
If that didn't work, do you have an ext partition? Is your cache bind mounted to /sd-ext? Can you post the output of the
df -h
command? I suspect your cache is not bind mounted.
Sent from my Gingerbread on Dream using XDA App
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/secure/asec
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/secure/asec
Thanks for help
I have re-flashed the rom and the problkem seems to be solved. Thanks for help.
P.S: add rotary lockscreen to ADS_magpie?
gorneman said:
Thanks for help.
Click to expand...
Click to collapse
Prego.
gorneman said:
P.S: add rotary lockscreen to ADS_magpie?
Click to expand...
Click to collapse
Sorry, I tried it already some time ago, but there are too many dependencies to other parts of the CM sources. At the moment I don't think that I will invest the time to port it to ADS_Magpie, but we will see.

[Q] How to push file - No space left error

I am trying to push framework-res.apk file with ADB to my Galaxy S device but I get following error:
C:\>adb push framework-res.apk /system/framework
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': No
space left on device
After checking available space with adb shell df -h command, I get:
Filesystem Size Used Available Use% Mounted on
tmpfs 168.4M 32.0K 168.3M 0% /dev
tmpfs 168.4M 0 168.4M 0% /mnt/asec
tmpfs 168.4M 0 168.4M 0% /mnt/obb
/dev/block/stl9 275.8M 272.0M 3.8M 99% /system
meaning that I have enough space to push Framework file. Where is the problem?
Thanks.
Stile35 said:
I am trying to push framework-res.apk file with ADB to my Galaxy S device but I get following error:
C:\>adb push framework-res.apk /system/framework
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': No
space left on device
After checking available space with adb shell df -h command, I get:
Filesystem Size Used Available Use% Mounted on
tmpfs 168.4M 32.0K 168.3M 0% /dev
tmpfs 168.4M 0 168.4M 0% /mnt/asec
tmpfs 168.4M 0 168.4M 0% /mnt/obb
/dev/block/stl9 275.8M 272.0M 3.8M 99% /system
meaning that I have enough space to push Framework file. Where is the problem?
Thanks.
Click to expand...
Click to collapse
I don't know if I get it right or not, but I guess the 3.8 MB is your free space left on system partition. I think you should have at least 2 MB of space left always (after pushing the file). That is needed because of the rfs filesystem.
If this is the case, I recommend deleting some of the stock system apps (mini diary, y finance clock, voice dialer, fonts, etc, you can find many guides for this) using titanium backup app (you can get it from the market). I hope I could help
Sent from my sgs Please hit thanks!

/sbin/.magisk/mirror/system at 100%?

Hi all,
I just did an update on my OnePlus 3T from Android 8 to Android 9 that went wrong so that I had to do a factory reset. Well, damn. So here I am with a freshly installed Android 9 / OOS 9.0.3.
Magisk 19.3 is installed and I wanted to configure Adaway but Adaway told me upon activation of the new hosts file that there's no space on the device left.
That's what it looks like:
Code:
OnePlus3T:/ $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 2.7G 9.2M 2.7G 1% /
tmpfs 2.7G 1.4M 2.7G 1% /sbin
tmpfs 2.7G 804K 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
/dev/block/sde20 2.8G 2.8G 0 100% /system
none 2.7G 0 2.7G 0% /sys/fs/cgroup
/dev/block/sda3 248M 4.3M 238M 2% /cache
/dev/block/sde12 12M 4.1M 7.2M 37% /system/vendor/dsp
/dev/block/sda2 27M 776K 26M 3% /mnt/vendor/persist
/dev/block/dm-0 113G 16G 97G 15% /data
/data/media 113G 16G 97G 15% /storage/emulated
OnePlus3T:/ $ su -
OnePlus3T:/ # df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 2.7G 9.2M 2.7G 1% /
tmpfs 2.7G 1.4M 2.7G 1% /sbin
tmpfs 2.7G 804K 2.7G 1% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
none 2.7G 0 2.7G 0% /sys/fs/cgroup
/dev/block/sda3 248M 4.3M 244M 2% /cache
/dev/block/sde12 12M 4.1M 7.5M 36% /system/vendor/dsp
/dev/block/sde11 95M 82M 13M 87% /system/vendor/firmware_mnt
/dev/block/sde23 1.0G 128K 1.0G 1% /system/vendor/bt_firmware
/dev/block/sda2 27M 776K 27M 3% /mnt/vendor/persist
/sbin/.magisk/block/system 2.8G 2.8G 4.0M 100% /sbin/.magisk/mirror/system
/sbin/.magisk/block/data 113G 16G 97G 15% /sbin/.magisk/mirror/data
/data/media 113G 16G 97G 15% /mnt/runtime/default/emulated
Where does /sbin/.magisk/mirror/system come from and is there any way to resize that partition? Or does anyone have a clue on how to resolve this without removing system/vendor apps (as they're getting reinstalled on the next update)?
If OnePlus decided to fill up the system partition, then the Magisk system mirror will be full as well.
What you want to look at though is /system, not /sbin/.magisk/mirror/system. The latter is simply the real system partition and the former is Magisk's systemless mask.
Since it's full you're going to have to do some workarounds... Like creating a Magisk module to mount the hosts file of your choice directly.
Well, that's pretty unfortunate from OnePlus. As suggested I did it with the systemless hosts and it works fine. Thanks a lot!

Categories

Resources