Hi.. how i can mount/remount sdcard in console? because something is wrong.. in every roms when i goes to sdcard in setting its show unavailable.. once time ago i wrote something in console as remount and it was okey.. but i forgot it how i can do that.. i tried many combination of command mount but nothing. maybe i can find in google with keyword "mount/remount in linux" can be possible?
but through astro i can explore sdcard.. its strange..
please help. And thanks for answers
Code:
mount /dev/block/mmcblk0pN /sdcard -t FSTYPE
N is number of partition (usually 1) and FSTYPE is vfat or ext2 (usually vfat)
Google is a good help so please use it!
i look on mount and sdcard is mounted.. but still i cannot explore it with anything except astro.. i think maybe is problem in kernel.. i have last kernel version... working sdcard full for everyone? maybe is problem only in my phone.. or its global error
Sd card works in latest kernel, probably is your problem, reformat the card.
Try this:
vdc volume mount /sdcard
Currently, the /sdcard folder is pointing to the phone memory. My external card is mounted as /sdcard/external_sd
The problem with the above structure is that all the stuff that should be stored in the actual sdcard is stored in the memory.
I am sure there is a way to mount the external sdcard as /sdcard in the system through shell commands. Can someone help me with this?
Thanks.
1. I believe you need root in order to manipulate mounting points...
2. Be careful manipulating mount points as this may break aps looking for data in the /sdcard mount point...
YMMV
Chinook Pilot said:
1. I believe you need root in order to manipulate mounting points...
2. Be careful manipulating mount points as this may break aps looking for data in the /sdcard mount point...
YMMV
Click to expand...
Click to collapse
1. I am rooted.
2. Well, I want to change the /sdcard mountpoint to the actual sdcard. I don't think this should break anything. I am not sure about the syntax, that is why I am asking.
Mount
Here's a link to the man pages for the mount command. I'm not running a stock kernel so my mount points and fstab aren't generic to the stock e4gt... Basically you need to umount both and the mount where you wish them to point... Good luck...
http://linux.die.net/man/8/mount
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
I'm new to The S3 and the new MTP device connection, but I searched and can't seem to find any similar problems... That being said I flashed CWM to my S3(twice because Samsung has this annoying habit of overwriting your recovery if you don't delete a few system files) anyway su.zip flashed fine and after I had my phone the way I wanted it(still stock 4.0.4) I was going to do a nandroid backup but I get an error "Can't mount backup path" I also can't mount /sdcard form the mount menu... But i can still choose zips form my SD card. So I'm a little lost
I only deleted
/system/recovery-from-boot.p and /system/etc/install-recovery.sh
and I am running the Telus "M" version with no modifications other than SU and the deleted system files... I'm thinking this is some error with MTP or something along those lines so any help would be great!
Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
I'm having the same type of problem with my E:\ not being mounted when I go into twrp. I can't even see a directory for me to run the wipe command on.
Will you try restoring back to Factory ROM ?
peterNYC said:
Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
Click to expand...
Click to collapse
Do you have root access ?
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Odin back to stock or try a different recovery, might I suggest CWM
fattest said:
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Click to expand...
Click to collapse
Your best bet is to odin back to Stock, mine is a bit weird, I can't install JB via no method, always stuck at samsung logo, but ICS seems to go ok, you should try it.