Can someone post the script that mount sdcard at boot?
I created a kernel but it doesn't mount sdcard at boot, it's possibile to create the script in system/etc/init.d that mount sdcard at boot?
Try busybox mount while booted to see if it's possible to mount SD Card with a script. SD card mounts automatically if it's FAT32 and it takes a little vold.fstab configuration for other file systems. You should check franco's or LG's kernel to see how to automount sd card from kernel.
This is taken from CM7, put it in init.d and see.
Turducken said:
This is taken from CM7, put it in init.d and see.
Click to expand...
Click to collapse
Thank you very much but what's that?
# set property with exit code in case an error occurs
setprop cm.e2fsck.errors $e2fsk_exitcode;
if [ "$e2fsk_exitcode" -lt 2 ];
then
# mount and set perms
$BB mount -o noatime,nodiratime,barrier=1 -t ext3 $SD_EXT_PART $SD_EXT_DIRECTORY;
if [ "$?" = 0 ];
then
$BB chown 1000:1000 $SD_EXT_DIRECTORY;
$BB chmod 771 $SD_EXT_DIRECTORY;
log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";
else
log -p e -t mountsd "Unable to mount filesystem for $SD_EXT_DIRECTORY!";
fi
else
log -p e -t mountsd "Unable to repair filesystem, disabling apps2sd";
fi
Click to expand...
Click to collapse
EDIT: Mount This script sdcard?
#!/system/bin/sh
mount -o remount,ro -t yaffs2 /dev/block/mmcblk0
Click to expand...
Click to collapse
RE-EDIT: The CM7 script doesn't works, in the second reboot the sd wasn't mount
The CM7 script mounts a2sd apps (apps2sd script). The second one should be like
Code:
mount -o remount,r[b]w[/b] -t [b]fat32[/b] /dev/block/mmcblk0
. As I already said, it's probably a kernel problem, vold mounts sdcards automatically.
Cricco said:
Thank you very much but what's that?
Click to expand...
Click to collapse
That part of the script mounts an ext partition if one exists.
RE-EDIT: The CM7 script doesn't works, in the second reboot the sd wasn't mount
Click to expand...
Click to collapse
As Ianis G. Vasilev said there are various ways to mount the SD card but I suspect the issue is with the kernel you've compiled. Flash francos, if it mounts then your kernel is bad. Run logcat to see what's going on.
**EDIT**
I didn't see Ianis post before I began mine...
so with
mount -o remount,rw -t fat32 /dev/block/mmcblk0
Click to expand...
Click to collapse
the sd will be mount?
EDIT: I need a script that mount sd without write or read permission, infact if i use root explorer and I go to sdcard sometimes the sdcard folder is blank, so the sd didn't mount
Read permissions are needed to see what's on the sd card. For a read-only mount replace rw with ro:
Code:
mount -o remount,r[b]o[/b] -t fat32 /dev/block/mmcblk0
I would advice you to use dmesg(should be enabled in kernel) to see if your phone detects the card and logcat to see if any errors are preventing your card from mounting.
Now i create script
#!/system/bin/sh
mount -o remount,rw -t fat32 /dev/block/mmcblk0
mount -t vfat -o /dev/block/mmcblk0
Click to expand...
Click to collapse
is it correct?
I have an Acer A210 and have modified the boot.img to have ro.secure=0 and ADB root. Then I had to mount the /system partition but that is not so easy:
Code:
C:\>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
C:\>adb push busybox /data/local/tmp
1065 KB/s (777216 bytes in 0.712s)
126|[email protected]:/data/local/tmp # chmod 755 busybox
chmod 755 busybox
[email protected]:/data/local/tmp # ./busybox mount -o remount,rw /system
./busybox mount -o remount,rw /system
mount: permission denied (are you root?)
Currently the only way to mount /system rw is this:
Code:
cd /system/xbin/
mount -o remount,rw /dev/block/platform/sdhci-tegra.3/by-name/APP /system/
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
MaluNoPeleke said:
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
Click to expand...
Click to collapse
Acer implemented in kernel "system RW protection" (I don't know how to call that)- kernel prohibits such operations. Only workaround is compiling a custom kernel with this feature disabled.
As for recovery- check /etc/fstab if sdcard mountpoint (stored in init.rc or init.[device name].rc) matches the one recovery uses (/etc/fstab)
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
How can I check the fstab content in the recovery? It was built by the recovery builder.
Thanks!
MaluNoPeleke said:
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
Click to expand...
Click to collapse
It's a kernel config option only, for a510 it's CONFIG_ACER_SECURE_MOUNT and it is accessible in menuconfig or by hand- in .config change "CONFIG_ACER_SECURE_MOUNT=yes" to "# CONFIG_ACER_SECURE_MOUNT is not set" (as for kernel compilation- there are many tutorials floating around)
MaluNoPeleke said:
How can I check the fstab content in the recovery? It was built by the recovery builder.
Click to expand...
Click to collapse
Start recovery and just
Code:
adb shell
cat /etc/fstab
or
Code:
adb pull /etc/fstab [path on your pc]
I've never used any recovery builder but kernel and ramdisk/initramfs (where recovery is placed) are separate files, you can unpack boot.img and just modify what you need (note- linux machine required, virtual one will do)
Is it already disabled in the source code?
Code:
[email protected] ~/Dokumente/kernel $ grep -R -i 'CONFIG_ACER_SECURE_MOUNT*' ./*
./arch/arm/configs/picasso_mf_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_m_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./fs/Makefile:ifeq ($(CONFIG_ACER_SECURE_MOUNT),y)
It seems that it's disabled.
Is there a zip file for Acer 210 tablet now 4/2013
dobie62 said:
Is there a zip file for Acer 210 tablet now 4/2013
Click to expand...
Click to collapse
There is a real lot available for A210:
Pure root (German)
CWM recovery (German)
Custom Kernel
CM 10.1 like ROM
What are you looking for?
regards Uwe
This is it but in English please.
A210
Are the A210 and the A510 similar enough to use the same kernel, ROM's or Recovery?
Hi,
As the title says, Is there Kernel loop support for our LG Optimus L9 ?
I'm trying to mount a loop file created on debian on the device, but I get the error
ioctl LOOP_SET_FD failed: Device or resource busy
Click to expand...
Click to collapse
.
This is what I did --
Loop file created on debian and formatted with ext4.
On Optimus L9 with CM10.1, in terminal emulator,
$su
#losetup /dev/block/loop0 /storage/sdcar1/file
#mount -o remount,rw /system
#mkdir /system/temp
#mount -rw -o loop -t ext4 /dev/block/loop0 /system/temp/
ioctl LOOP_SET_FD failed: Device or resource busy
#
Click to expand...
Click to collapse
Is our kernel having loop support. If yes, am I doing anything wrong? The file gets successfully mounted in Debian.
EDIT:
using "busybox mount" solved the issue.
Tried adding busybox to the mount command and voila it worked.
#busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system/temp/
Click to expand...
Click to collapse
You just taught me something new, thanks.
Can you upload your img, I would really like to check this out, or can you direct me to a thread so I can learn some more.
Sent from my LGMS769 using xda app-developers app
kuma82 said:
You just taught me something new, thanks.
Can you upload your img, I would really like to check this out, or can you direct me to a thread so I can learn some more.
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
The one I created is over 100MB. I had a html tutorial containing 12,000 files. I don't want to put those files on sdcard and mess it up. So, I used this block device.
I have created a sample "temp.img" file with a size of 500KB. It contains a single text file. I'm attaching it and you can check it out.
Below is the way i created and mounted it.
Code:
# "temp.img" md5 b97642fed817fa3f1a0cc6dc64b6c40d
# remount rootfs rw.
mount -o remount,rw /
# create mount point.
mkdir /mnt/temp
# chmod mountpoint.
chmod 777 /mnt/temp
# create block file.
dd if=/dev/zero of=/storage/sdcard0/temp.img bs=1024 count=500
# this creates 500 KB file. I can't seem
# to get bs=1M argument working on android.
# so bs1024 x count = target file size (=count times in KB).
# query free loop device. (will be /dev/block/loopx)
losetup -f
#attach block file with free loop.
losetup /dev/block/loop0 /storage/sdcard0/temp.img
#create file system.
mke2fs -T ext2 /dev/block/loop0
# And finally mount it
busybox mount -o loop -t ext2 -rw /dev/block/loop0 /mnt/temp
# For unmounting
busybox umount /mnt/temp
And it isn't encrypted. I don't need encryption, and i can't even seem to figure out how to encrypt it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BusyMount 1.01 for the Rooted Fire TV
DOWNLOAD HERE
BusyMount is combination utility comprised of BusyBox v1.22.1
and bash scripts that persistently mount multiple USB mass
storage devices on your Fire TV. Of course it works just as well with a
single USB stick.
It has been tested with 4 concurrently mounted drives (vfat,exfat,ntfs,ext4).
BusyMount's two primary scripts live in /system/xbin:
mntdrives1.sh
mntdrives2.sh
The mntdrives1.sh script should run as is on any rooted Fire TV and mount your drives/sticks at /storage/usb/driveX where X is the sequence number of the device on your system: e.g. sda1=drive1, sdb1=drive2, etc.
The mntdrives2.sh script will mount your drives via their UUID, an internal label that is applied when the drive is formatted. If you have more than one drive attached to your Fire TV this is very important.
It is not at all unusual for the operating system to switch /dev/block/sd?? addresses so one boot your movies drive is called /dev/block/sda1 and anime /dev/block/sdb1. Reboot or swap drives and suddenly they have different addresses, sdc1 and sdd1. XBMC will not appreciate this. Mounting via UUID makes sure your data is in the same place every time.
mntdrives2.sh uses the same driveX naming scheme for mountpoints, but you can control what mounts where.
Each script can be called at boot to automount your drives. Currently, this is done via install-recovery-2.sh and busybox run-parts.
BusyMount is installed via Clockwork Mod provided by [email protected], something that is a must have for your rooted Fire TV. If you don't have it install it now, and then come back here! *
To install BusyMount:
1. adb connect 111.222.333.444 (substitute your FireTV IP address)
2. adb push filename.zip /sdcard/
3. adb shell su -c reboot recovery
Once in ClockworkMod Recovery:
Choose zip from sdcard
Choose 0
Scroll to BusyMount zip file
Press Enter
Select Yes
BusyMount will install. When it's finished, reboot. When the Fire TV reboots your drives will have been mounted by mntdrives1.sh. For mounting by UUID you will need to edit mntdrives2.sh. Instructions in the next post.
* you can also download BusyMount without the CWM installer at the link above for manual installation
IMPORTANT: Windows users: do NOT edit the mntdrives2.sh file with notepad! It will break the script. Instead, use busybox vi or pull the file to your computer and use Notepad++. Be sure to make backups of the scripts before editing!
To mount drives via UUID, first you need to find out what they are. After installing BusyMount, ADB shell or sshhttp://www.jocala.com/busydrop.html into your Fire TV. If you entered via adb su to root and issue the command:
Code:
blkid /dev/block/sd*
You should see something like this for as many drives as you have attached:
Code:
[email protected]:/ #blkid /dev/block/sd*
/dev/block/sdi1: LABEL="firetv1" UUID="94f2a28c-caac-4eb7-a544-84a650c0b809" TYPE="ext4"
/dev/block/sdh1: LABEL="CRUZER" UUID="138FD3254AEAB65E" TYPE="ntfs"
/dev/block/sdf1: LABEL="VFAT" UUID="0577-07FC" TYPE="vfat"
/dev/block/sdb1: LABEL="ExFat" UUID="544D-B43D" TYPE="exfat"
The important bits are the sd?? drives's "UUID=XXXXXX"
Now we edit the mntdrives2.sh file
If you're editing directly on the device mount /system as r/w:
Code:
mount -o remount,rw /system
Here is the mntdrives2.sh file:
Code:
#!/system/bin/sh
sleep 20
#
# FireTV USB/UUID Drive Mounter
#
# REQUIRED: Busybox with suuport for run-parts, blkid, mount-helper
# mount-helper and stuff that's probably slipped my mind required.
# AFAIK, NONE of the "free" Play Store busyboxes have all of the
# supplied options. I suggest you use mine or compile your own.
# Replace the UUIDs below with the UUIDs
# from your drives. This script has been tested
# with 4 drives mounted (vfat,exfat,ntfs,ext4)
# but (in theory) should support 26 (sda1-sdz1)
#
# Enjoy! [email protected]
#
export uuid1="544D-B43D"
export uuid2="138FD3254AEAB65E"
export uuid3="94f2a28c-caac-4eb7-a544-84a650c0b809"
export uuid4="0577-07FC"
i=0
storage="/storage/usb"
if [[ $(ls /dev/block | $busybox grep -c 'sd') -eq 0 ]]; then
exit 0
fi
mount -o remount,rw / ;
for f in /dev/block/sd??; do
drive=`echo $f | sed -r 's/^.{11}//'`
mountType=$(busybox blkid $f | busybox sed -n -e 's_^.*TYPE="\([^\"]*\)".*_\1_p');
mountUUID=$(busybox blkid $f | busybox sed -n -e 's_^.*UUID="\([^\"]*\)".*_\1_p');
i=$((i+1))
if [[ $mountUUID == $uuid1 ]]; then
busybox mkdir -p $storage/drive$i;
mount.exfat-fuse -o rw $f $storage/drive$i
fi
if [[ $mountUUID == $uuid2 ]]; then
busybox mkdir -p $storage/drive$i;
ntfs-3g $f $storage/drive$i -o rw,sync
fi
if [[ $mountUUID == $uuid3 ]]; then
busybox mkdir -p $storage/drive$i;
busybox mount UUID=$uuid3 $storage/drive$i
fi
if [[ $mountUUID == $uuid4 ]]; then
busybox mkdir -p $storage/drive$i;
busybox mount UUID=$uuid4 $storage/drive$i
fi
done
mount -o remount,ro /
As you can see there are 4 UUIDs defined at the top of the script. These are my personal UUIDs so of course these are the edits you have to make. Very simply, just change uuid1:
Code:
export uuid1="544D-B43D"
to your uuid1:
Code:
export uuid1="4455X-G5553" (or whatever)
Rinse and repeat for as many drives as you wish to define. Good luck!
reserved
This looks very interesting. Will try it out on the next Fire TV I set-up. Nice work!
So just to be clear, this simply serves to provide additional external storage to the FireTV, kinda like what we have had with StickMount?
It's not a way to expand internal storage like jmandawg's method, or to maximize internal storage space (without expansion) by using the StickMount/Link2SD combo, or is it?
AQKhanTheOne said:
So just to be clear, this simply serves to provide additional external storage to the FireTV, kinda like what we have had with StickMount?
It's not a way to expand internal storage like jmandawg's method, or to maximize internal storage space (without expansion) by using the StickMount/Link2SD combo, or is it?
Click to expand...
Click to collapse
It mounts multiple drives by sd device name or by UUID like paid stickmount. However, as you can see by the attached script, it can also use croniccorey & jmandawg's handy technique to mount an external drive as /data, tricking the aftv. I mount by UUID which gets around the "only one drive & /dev/sda1 only" problem.
BTW, the attached script has a .c extension because sh isn't allowed. If you play with it you'll want rbox's recovery installed. Right now my FTV has a 1TB ext4 drive for media, a 500Gb ext4 drive for /data, plus vfat and exfat drives attached just for the hell of it. Which I think is pretty damn sweet.
jocala said:
It mounts multiple drives by sd device name or by UUID like paid stickmount. However, as you can see by the attached script, it can also use croniccorey & jmandawg's handy technique to mount an external drive as /data, tricking the aftv. I mount by UUID which gets around the "only one drive & /dev/sda1 only" problem.
BTW, the attached script has a .c extension because sh isn't allowed. If you play with it you'll want rbox's recovery installed. Right now my FTV has a 1TB ext4 drive for media, a 500Gb ext4 drive for /data, plus vfat and exfat drives attached just for the hell of it. Which I think is pretty damn sweet.
Click to expand...
Click to collapse
Yes it is! I did have a couple of questions though. One is that would StickMount still be needed? And if I partition a HDD (or a USB stick) into 2 or more partitions, would these partitions have different UUID's?
AQKhanTheOne said:
Yes it is! I did have a couple of questions though. One is that would StickMount still be needed? And if I partition a HDD (or a USB stick) into 2 or more partitions, would these partitions have different UUID's?
Click to expand...
Click to collapse
Stickmount's not needed on FTV in any case. I've been mounting drives with adbFire since v1.01 (v1.12 is current) although mounting by UUID is new. Each partition get's its own UUID when formatted and can be mounted by it. BTW, you can also mount by label, eg drives labeled "movies", "data", etc.
jocala said:
Stickmount's not needed on FTV in any case. I've been mounting drives with adbFire since v1.01 (v1.12 is current) although mounting by UUID is new. Each partition get's its own UUID when formatted and can be mounted by it. BTW, you can also mount by label, eg drives labeled "movies", "data", etc.
Click to expand...
Click to collapse
Cool. Thanks for the answers! This should (will) become the preferred method for external storage on the FTV!
AQKhanTheOne said:
Cool. Thanks for the answers! This should (will) become the preferred method for external storage on the FTV!
Click to expand...
Click to collapse
I think /data swap will need automation for many. Everyone's not comfortable with the command-line. I'm working on an adbFire function to grab a uuid and write out a mount script, but it won't be ready for the next update
jocala said:
I think /data swap will need automation for many. Everyone's not comfortable with the command-line. I'm working on an adbFire function to grab a uuid and write out a mount script, but it won't be ready for the next update
Click to expand...
Click to collapse
Has this been incorporated into the latest version of adbFire?
AQKhanTheOne said:
Has this been incorporated into the latest version of adbFire?
Click to expand...
Click to collapse
Yes, but automation's not done for UUID mounting. I hope to have that finished for the next update.
hi could someone help, i installed this using adbfire and manage to edit the mntdrives2.sh locally
but i cant seem to be able to push this to system
Ive tried:
adb shell
su
mount -o remount,rw /system
adb push mntdrives2.sh /system/xbin/
i probably have a command wrong somewhere
DEREKTROTTER said:
hi could someone help, i installed this using adbfire and manage to edit the mntdrives2.sh locally
but i cant seem to be able to push this to system
Ive tried:
adb shell
su
mount -o remount,rw /system
adb push mntdrives2.sh /system/xbin/
i probably have a command wrong somewhere
Click to expand...
Click to collapse
(This is all built-into adbFire already)
In this case, adb push should be run from the pc, not the android device.
Code:
adb connect your.ip.address:5555
adb push mntdrives2.sh /sdcard
Or use adbFire to push the file to /sdcard
We aren't currently running a rooted kernel, so you can't push directly to /system or /data. You have to push to /sdcard, then shell into the device and do the remainder as root:
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/mntdrives2.sh /system/xbin
chmod 0755 /system/xbin/mntdrive2.sh
mount -o remount,ro /system
(using ssh's scp you can copy stuff anywhere on the device and bypass the preliminary push to /sdcard...scp runs as root.)
Edit: I strongly suggest having CWM Recovery installed before rebooting with untested scripts!
thanks i will try this later
and ye i have CWM installed
DEREKTROTTER said:
thanks i will try this later
and ye i have CWM installed
Click to expand...
Click to collapse
Good luck
^ the above didnt seem to work, not sure why
DEREKTROTTER said:
^ the above didnt seem to work, not sure why
Click to expand...
Click to collapse
Check your spelling of mntdrives2.sh -- you typed mntdrive2.sh
jocala said:
Check your spelling of mntdrives2.sh -- you typed mntdrive2.sh
Click to expand...
Click to collapse
lol thanks, ill try again
its because i copied straight from your post above
edit: file transfer was a success and it still boots up fine
I assigned my NTFS drive as uuid4 but it still mounts as drive1. Is it because i need multiple attached? I dont have more drives available to test atm.
DEREKTROTTER said:
lol thanks, ill try again
its because i copied straight from your post above
Click to expand...
Click to collapse
That was a test to see if you were paying attention <g>
DEREKTROTTER said:
edit: file transfer was a success and it still boots up fine
I assigned my NTFS drive as uuid4 but it still mounts as drive1. Is it because i need multiple attached? I dont have more drives available to test atm.
Click to expand...
Click to collapse
No, you can mount one drive or many. Post your script and let's see.