BusyMount v1.01 - Fire TV Android Development

{
"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.