Related
Can someone explain how I can delete a file from the SDcard, yet still see it and open it on my drive in Windows? Also, why can't I see files placed on my SDcard from Windows until I reboot my device...
I created this script in attempt to fix the second issue, I think it works okay most of the time... Issue arise only if it can't unmount /sdcard successfully.
Code:
umount -f /dev/block/mmcblk0p1
mount -o rw,noatime,nodiratime,fmask=0000,dmask=0000,iocharset=iso8859-1,flush -t vfat /dev/block/mmcblk0p1 /sdcard
how can i modify the content of factoryfs.rfs so that the file is flashable with odin?
i know how to extract the files but not how to modify the content directly.
i've tried to do it directly on the device, but i can only mount is as vfat and not rfs, so modifications are not saved correctly after unmounting...
here are my commands:
this works but i can't make changes that are saved
/tmp # mount -o loop /sdcard/external_sd/factoryfs.rfs rfs/
for some reason mounting as rfs does not work, how can i fix this?
/tmp # mount -t rfs -o loop /sdcard/external_sd/factoryfs.rfs rfs/
mount: mounting /dev/loop19 on rfs/ failed: No such device
read here http://forum.xda-developers.com/showthread.php?t=751827&page=3
without rfs support for linux it is impossible
yes i know that but i try to mount it on the device itself and there we should have rfs support
I am new to Android, want to customize the system follow the tutorials, but found the Note is different to other Android phones:
for other phone, there will be a /proc/mtd and list all the partitions with mount point, but on Note I can only found /proc/fs, with 3 folders: ext4 jbd2 nfsd
and the mount table is like this:
rootfs on / type rootfs (ro,relatime)
...
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
for other devices, e.g., HTC Wildfire, the partition will like below:
mtd1: recovery
mtd3: system"
...
I downloaded the CF-Root flasher, by Chainfire, found basiclly it's flashing a zImage into /dev/block/mmcblk0p5. I mount the partition before flash and seems there is only some picture files there. how can we know the machine will boot to this partition in recovery mode?
nobody knows? so far what I get seems that the phone do not use the /recovery partition, but use same kernel to handle the recovery state. during boot it will search for /system/etc/install-recovery.sh, maybe that will trigger the recovery process?
The Note, like many other Samsung phones, does not use or follow the mtd layout - at all.
Indeed there is a single kernel for both normal boot and recovery. Normal boot uses init.rc script, recovery boot uses recovery.rc script.
There is a "spare" partition that is both called recovery and available, but it isn't used.
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
FaxXer said:
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
Click to expand...
Click to collapse
u need a kernel that supports ext3. u can ask one of the guys compiling at the moment if they have time to add an ext3 module for u.
May be a stupid question:
would ext4 work instead? I thought the system partition would use this FS.
filesystem is already ext4
wintel_mac said:
May be a stupid question:
would ext4 work instead? I thought the system partition would use this FS.
Click to expand...
Click to collapse
well the system uses ext4 so it should work, but i'm not sure what u're trying to achieve. i use a 16 gb class 10 formatted fat32
Blumdum said:
filesystem is already ext4
Click to expand...
Click to collapse
He's talking about formatting external sd-card
When I get him right, he has a file that exceeds the 4GB FAT32 limit.
So he looks for an alternative to FAT32, which might be some kind of ext*-FS.
wintel your right!
In the Android-Hilfe Forum someone said the system expect first an vfat partition and then the ext. I think thats wrong cause its not working but somehow it has to go.
Hmm should I write these mount command I postet in the init.rc? Or something else. Would be very nice if you post your ideas!
Thanks
init.rc+ ext3 module/object included in kernel
Hmm okay thats good but how do I use them? So I can read and write to my external sd card with an ext3 or ext2 partition.
Thanks
Come on guys where are the great developers?!
Ok I did a test with busybox inbuilt mount, but I tried only with an image.
Not with a real SD card! This worked for me:
On a linux box:
# dd if=/dev/zero of=/tmp/image bs=1M count=1k
# mkfs.ext4 /tmp/image
Copy file to your phone. Then:
On the phone with terminal:
# mkdir /sdcard/mmnt
# busybox mount -o loop /sdcard/image /sdcard/mmnt
To unmount:
# busybox umount -l /sdcard/mmnt
Anybody tried that?
If I understand u right u puting an image file (ext3/4) on the sd and mount that as a virtual disk. Wouldn't the image file be bound to the same restrictoins as other content on a fat32 file system? Like the 4 gig limit!
YOU WILL LOSE ALL DATA ON YOUR SDCARD IF YOUR FDISK
BACKUP WHATEVER IS ON THERE FIRST!!!
YOU'VE BEEN WARNED
using a photon 4g but....
what i did was get an external sdcard reader writer...
(used ubuntu) and let it mount
fdisk device and DELETE ALL PARTITIONS
write
fdisk again
create a linux primary type 83
type mount and grab the /dev/sdcX value (it was /dev/sdc1 for me)
umount that
then
mkfs.ext3 /dev/sdcX ... ( heres the thing though with cyanogen mod 7 kernel 2.6.32.9 SMP PREEMPT)
had to reboot twice for it to be seen in file manager...
its buggy but it does work for the most part
Reviving an old thread, but I just found that I can format a MicroSD under NTFS and it will work with Paragon's NTFS module. At the very least, my phone will mount the drive. I partitioned and formatted it with ext4 on my Linux machine and it didn't recognize it, but I did have it use the GUID partition table. Hoping to be able to load up some videos to take with me.
ext4 sdcard mount works
FaxXer said:
Hey,
I like to mount my external SD Card as ext3 to support large files. The SD Card is formatted with ext3 but now Android shows only an empty folder.
So i tried to remount the SD:
Code:
mount -o rw,remount -t ext3 /dev/block/vold/197:33 /mnt/sdcard/externald_sd
But it doesnt use something... Does anybody has an idea? Some Example or sthing else?
Greetz
Click to expand...
Click to collapse
The problem is with the shell interpreting the special character ":"
To make it work, first create a symlink to the device node:
Code:
ln -s /dev/block/vold/197\:17 /dev/sd2
Then mount it:
Code:
busybox mount /dev/sd2 /mnt/tmp
Code:
sh-4.1# ls -l /dev/sd2
lrwxrwxrwx root root 2013-11-16 14:45 sd2 -> /dev/block/vold/179:17
sh-4.1# mount|grep sd2
/dev/sd2 /mnt/tmp ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
success mounting ext formatted SD Card on Android
An improvement in technique to mount ext formatted SDcard:
1) be root and open terminal
2) insert the card
3) see the block device and partition names from dmesg
4) mount device to location of choice (create the directory if needed)
Below is an example of an SD card with one ext4 partition on it
Code:
bash-4.1# dmesg | tail | grep mmc
<6>[20230.719541] mmc1: new high speed SDHC card at address 0007
<6>[20230.722803] mmcblk1: mmc1:0007 SD32G 29.3 GiB (ro)
<6>[20230.728352] mmcblk1: p1
bash-4.1# busybox mount /dev/block/mmcblk1p1 /data/mnt/sdcard2
tribh said:
An improvement in technique to mount ext formatted SDcard:
1) be root and open terminal
2) insert the card
3) see the block device and partition names from dmesg
4) mount device to location of choice (create the directory if needed)
Below is an example of an SD card with one ext4 partition on it
Code:
bash-4.1# dmesg | tail | grep mmc
<6>[20230.719541] mmc1: new high speed SDHC card at address 0007
<6>[20230.722803] mmcblk1: mmc1:0007 SD32G 29.3 GiB (ro)
<6>[20230.728352] mmcblk1: p1
bash-4.1# busybox mount /dev/block/mmcblk1p1 /data/mnt/sdcard2
Click to expand...
Click to collapse
Would this work just the same way with i9000?
After this, no more access to the extSD by the Windows PC but only with Ubuntu, right?
tetakpatak said:
Would this work just the same way with i9000?
After this, no more access to the extSD by the Windows PC but only with Ubuntu, right?
Click to expand...
Click to collapse
Since it's generic Linux kernel and busybox functionality it should work on any 'droid. The SDcard device name might be different than in the above example - you will see the correct device and partition names after you insert SDcard and run `dmesg | tail` on the tablet or phone.
(of course your device must be rooted and have busybox...)
Typically Windows is engineered not to recognise anything that does not come from Microsoft, so you will not be able to mount the Linux partition via Windows.
I was in the process of installing another OS as a dual boot option on my touchpad along with webOS.
When I remounted the boot partition rw using the command...
mount -o remount,rw /boot
a special character was accidentally inserted into the mount point name.
Now I had two boot mounts showing with the ls command, one with a special character showing as "boot?".
To fix this, I unmounted the boot partition, which left a file named "boot" in the root directory and a directory named "boot?". I was able to rename the" boot?" directory to "abcd" since the root name was taken by the file.
At this point, I'm not sure what the command should be used to remount the boot directory correctly. Please help quickly as I am unable to reboot at this time...
duh1 said:
I was in the process of installing another OS as a dual boot option on my touchpad along with webOS.
When I remounted the boot partition rw using the command...
mount -o remount,rw /boot
a special character was accidentally inserted into the mount point name.
Now I had two boot mounts showing with the ls command, one with a special character showing as "boot?".
To fix this, I unmounted the boot partition, which left a file named "boot" in the root directory and a directory named "boot?". I was able to rename the" boot?" directory to "abcd" since the root name was taken by the file.
At this point, I'm not sure what the command should be used to remount the boot directory correctly. Please help quickly as I am unable to reboot at this time...
Click to expand...
Click to collapse
What OS are you trying to install? What other commands did you run that's preventing you from booting? (based on what you've said you've run above, you should still be able to reboot since you haven't actually changed anything in /boot yet?) .
You could try: "rm /boot ; mkdir /boot ; mount -o remount,rw /boot" I guess.
If you told me more about what you are trying to do and what you have already done, I could help more.
And don't worry even if you have modified /boot such that it won't boot normally. I can help you correct that, but I'd like yo know more about what you are trying to do and what you have done so far.
jcsullins said:
What OS are you trying to install? What other commands did you run that's preventing you from booting? (based on what you've said you've run above, you should still be able to reboot since you haven't actually changed anything in /boot yet?) .
You could try: "rm /boot ; mkdir /boot ; mount -o remount,rw /boot" I guess.
If you told me more about what you are trying to do and what you have already done, I could help more.
And don't worry even if you have modified /boot such that it won't boot normally. I can help you correct that, but I'd like yo know more about what you are trying to do and what you have done so far.
Click to expand...
Click to collapse
I was reinstalling LuneOS and was in the process of making the /boot partition writable using the command....
mount -o remount,rw /boot
I had accidentally inserted a special character after /boot in the above command. This created two /boot entries as seen using the ls command.
One entry was /boot same as before, and a new entry shown as /boot? (the ? replaces the special character that cannot be displayed).
It seems I had created a second mount point with an undisplayable name.
I then issued an unmount command. to try to fix the issue...
umount /boot
This turned the /boot partition into a 6MB file named boot, and an empty directory named /boot? which I was able to rename to /abcd.
I cannot create or rename the directory to /boot since the file that now contains the boot filesystem currently has that name.
Deleting that 6MB boot file would delete the entire boot filesystem.
The command mount -o remount,rw /boot says can't find /boot in /proc/mounts
There is currently no /boot partition, just the file containing the filesystem, so I shouldn't reboot the system since there is no accessible bootloader.
I need to know the command to correctly mount the file as the /boot partition to the mount point /abcd, and then perhaps rename the mount point to /boot, or maybe rename the boot file to something else and then mount it to the /boot directory.
The mount command by itself would show how your /boot partition is currently mounted. and with what options -- maybe that would help recreate what mount command I should use to mount the boot file.
Thanks so much jc for your help in getting this fixed!
duh1 said:
I was reinstalling LuneOS and was in the process of making the /boot partition writable using the command....
mount -o remount,rw /boot
I had accidentally inserted a special character after /boot in the above command. This created two /boot entries as seen using the ls command.
One entry was /boot same as before, and a new entry shown as /boot? (the ? replaces the special character that cannot be displayed).
It seems I had created a second mount point with an undisplayable name.
I then issued an unmount command. to try to fix the issue...
umount /boot
This turned the /boot partition into a 6MB file named boot, and an empty directory named /boot? which I was able to rename to /abcd.
I cannot create or rename the directory to /boot since the file that now contains the boot filesystem currently has that name.
Deleting that 6MB boot file would delete the entire boot filesystem.
The command mount -o remount,rw /boot says can't find /boot in /proc/mounts
There is currently no /boot partition, just the file containing the filesystem, so I shouldn't reboot the system since there is no accessible bootloader.
I need to know the command to correctly mount the file as the /boot partition to the mount point /abcd, and then perhaps rename the mount point to /boot, or maybe rename the boot file to something else and then mount it to the /boot directory.
The mount command by itself would show how your /boot partition is currently mounted. and with what options -- maybe that would help recreate what mount command I should use to mount the boot file.
Thanks so much jc for your help in getting this fixed!
Click to expand...
Click to collapse
None of the commands you mention above would have created a FILE in / named boot.
If there is a FILE in / called boot, it is NOT your boot partition.
Also, the bootloader does not live in /boot.
Just reboot - nothing you mention above would prevent it from booting.
jcsullins said:
None of the commands you mention above would have created a FILE in / named boot.
If there is a FILE in / called boot, it is NOT your boot partition.
Also, the bootloader does not live in /boot.
Just reboot - nothing you mention above would prevent it from booting.
Click to expand...
Click to collapse
I no longer have access to moboot or the boot partition. If I reboot how can the system find the boot files?
Shouldn't I be able to see the boot partition it in fstab and remount the partition -- right now, it's not in there.
Can you test this on your own system, umount /boot then either see if you can regain access to it or reboot and see if there are no issues? Do you now have a file named boot in /?
duh1 said:
I no longer have access to moboot or the boot partition. If I reboot how can the system find the boot files?
Shouldn't I be able to see the boot partition it in fstab and remount the partition -- right now, it's not in there.
Can you test this on your own system, umount /boot then either see if you can regain access to it or reboot and see if there are no issues? Do you now have a file named boot in /?
Click to expand...
Click to collapse
I have absolutely no need at all to test it to know that it works.
If it's unable to boot, it's because of something other than what you mentioned above.
* Assuming you removed the /boot file and recreated the /boot dir. (i.e. "rm /boot ; mkdir /boot")
jcsullins said:
I have absolutely no need at all to test it to know that it works.
If it's unable to boot, it's because of something other than what you mentioned above.
* Assuming you removed the /boot file and recreated the /boot dir. (i.e. "rm /boot ; mkdir /boot")
Click to expand...
Click to collapse
Thanks jc and kudos -- you were right! The file named boot was an aberration, created by the badly formed mount command and a file I then copied to that location. I deleted the file and recreated the dir /boot.
I found the correct mount point /dev/root from another device, was able to mount /boot and device rebooted fine. Perhaps I didn't need to remount /boot before rebooting, but without some indication that it would be recreated, I didn't want to chance it.
Linux at times can be a painful learning experience, thanks for being here with the first aid, it's appreciated...