Related
Anyone have or know where I can download the telnetd binary for Android? I think I might have a way to get root privileges on the Samsung Moment...and if it works, I see no reason why it wouldn't work on the Hero.
Just need that darn telnetd binary and any of the support files so I can install it into my phone (as long as the root exploit works.) It's running Android 1.5 btw if that makes a difference.
Why not ssh?
Download dropbear
telnet is an open invitation to get hacked, since the connection is not encrypted.
I know telnet is not encrypted...that's why I'll turn off the radio and enable wifi when I do this.
I was on the IRC (#android-root on freenode) and was pointed in the direction of JesusFreke's build environment, in which (s)he has built a veritable ****-ton of ARM binaries that are *extremely* useful.
http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/
I found JFV1.51 CRB43 US BuildEnvironment (1324) to be particularly useful. Once extracted, I found binaries for a very full busybox, and a few dozen other useful goodies, including telnetd.
From the extracted tar, the binaries are under 'Build/System/ModifiedFiles/xbin'. adb push them to /data/local on the device, then call them via adb shell.
Example:
With device connected, and with the Android SDK installed and in your PATH:
Code:
# tar xvf JFv1.51_CRB43-US_BuildEnvironment.tar.gz
# cd Build/System/ModifiedFiles/xbin
# adb push <program of your choice> /data/local
# adb shell
# /data/local/<program of your choice>
Just out of curiosity...what is your hunch for getting root on the Moment?
@gargarxp - Thanks for the info!
gargarxp said:
Just out of curiosity...what is your hunch for getting root on the Moment?
Click to expand...
Click to collapse
I was looking through all of the recent kernel privilege level escalation reports, and ran across this one:
http://seclists.org/fulldisclosure/2009/Nov/105
It works on kernels up to 2.6.31...which the Moment runs 2.6.27. My plan is to use an Android app to execute this exploit contained in a native executable (which I have confirmed I can execute native code), which will then trigger a shell script I will write to copy the telnetd files into the proper places and start the service as root. From there, I'll telnet in...see if the root user has a password...and go from there.
Actually, if you get this to execute as root, the procedure from there is fairly simple.
From my understanding, the other root exploits have a singular goal: to gain a root shell for the purpose of creating a suid su for the system to use to gain root in the future. From the CDMA Hero process, once a root shell is gained:
Code:
# mount -o remount,rw -t rfs [COLOR="Red"]/dev/stl5[/COLOR] /system
# cd /system/bin
# cat sh > su
# chmod 4775 su
They:
Remount the /system fs as read-write
Go to the /system/bin directory
Copy sh to (a new) su
Set the permissions on that to 4 (SetUID) 775 (User-Group: RWX, Other: RX)
* The bit in red is what I observed the device mounted to /system to be on my Moment. I obtained this information by running adb shell mount and seeing what /dev device was next to /system. Should be the same for every Moment, but the procedure is useful for any Android (or Linux for that matter) device.
Once this is done, any user executing this su will do so as the user/group that the owns executable, which in this case is root:shell.
So, via this method, if you can manage to get a root shell on *any* Android device, bada bing bada boom: rooted.
...At least that is my understanding of it all.
Well...the problem is I can't get my Moment connected to my computer to run adb. I'm on Windows 7 64-bit...and the drivers won't load...and Samsung's PC Studio won't install properly. So, I found source code online for executing native code via an Android app...which should work to execute the native exploit.
And you'll have to excuse me...I've been using Linux for the past 10 years...programmed some projects on the platform...but this is pretty much my first time developing on Android.
Oh no problem at all. Frankly, I'm being overtly descriptive so as to make this post useful to the community in general and not be Moment-specific. I don't wish to encouter the ire of the XDA mods Just trying to do a public service.
So, do you have an ARM binary of the exploit built already (ImpelDown.c)? And if so, could you post a link to download it? I've never cross-compiled before and am currently going 10 rounds with gcc and the android-2.6.27 source tree.
Thank you! I know...it's kinda risky for me posting stuff about the Moment in an XDA forum...but I figure this could help the Hero efforts as well...and XDA was so good to me back when I was using my DIAM500...I wanted to contribute something back.
I'm still trying to get my cross-compiler built. I initially started out with Cygwin and a tool for building a cross-compiler...but that went horribly wrong...tons of compiler errors. I attempted to use Scratchbox on OpenSuse 11.2...but Scratchbox wants to run on a Debian system...ugh...haha.
And as I was typing my response to you...I decided to Google for "arm compiler windows" and found http://www.gnuarm.com/
But rest assured...once there's a working binary...I'll upload it here.
From the Gnash project's dev wiki....
http://wiki.gnashdev.org/Building_for_Android
They raise some issues with using a standard cross-compiler (GNUARM uses Newlib, which isn't the Android libc implementation Bionic...which is apparently a problem)
I grabbed the toolchain they link to on the page and am trying that.
Yeah...I found that out as well after I installed gnuarm...
I also just loaded the native toolkit.
Well gargarxp...I compiled it...ran it...didn't work. I'm going to try another one tomorrow.
I know Paul over at MoDaCo announced he has root but I think that should not prevent us from trying to figure it out ourselves.
I have been fiddling around with the device and its filesystem and, as some might have tried, most commands are very restricted and you can't even list the /system folder.
Recently I found a directory which has write permissions and installed busybox there through adb, here are the instructions:
Download a precompiled busybox binary from http://benno.id.au/blog/2007/11/14/android-busybox
Push it using adb: adb push busybox /data/local/rights
Start a shell: adb shell
Change directory to the folder: cd /data/local/rights
Give it execution permissions: chmod 755 busybox
Play around with it: ./busybox ls /system
Figure out how we can use the new capabilities to root the phone
Any thoughts?
I was trying something also.. although I dont really know what I am doing mostly, I was trying to use some kernel exploits to get root access without luck. Good learning experiece though..
It would be nice if he gave a hint..
update: This method is for use with Temp-Root with Visionary app. For permanent root, you can just use the adfree app, which is free in the market. Alternatively, you can still use the manual temp-root method with permanent root if you don't want an extra app. Just run the adblock-startup.sh file once, and then use the wget script whenever you want to do an update of the hosts file!
After trying out a few things to get ad free working on startup, I was able to get it going without actually using the app. I used the basic concept of the app, but basically am performing it in command lines.
For this, I used GScripts to run/edit scripts, and Visionary to do a temp-root.
If you want to skip all of this, and go to a completely automated script, see updates at bottom.
First, create a script, adblock-wget.sh, to download the latest hosts file which blocks certain sites. It pulls the file from a website that contains updated hosts files and stores it in /data/data/:
##adblock-wget.sh##
Code:
wget http://209.68.48.119/winhelp2002/hosts.txt -O /data/data/hosts
This can be done in GScripts, and run every couple days to get the latest copy. Make sure you have SU checked in the script.
Second, we need to make another script, adblock-startup.sh which removes the existing hosts file in /system/etc/ and then create a symlink to the hosts file we just obtained on the internet in /data/data/
##adblock-startup.sh##
Code:
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -o remount,ro /dev/block/mmcblk0p25 /system
finally, you'll need to add this script to visionary.sh. if you created it in gscripts, one easy method is to long press the script in the menu, and save to SD. it'll be placed in your /sdcard/gscript/ folder.
to place this newly created script in visionary.sh, open up your current visionary.sh file, and place this line in it:
##visionary.sh##
Code:
sh /sdcard/gscript/adblock-startup.sh #change to correct directory
busybox killall system_server #this hot reboot is optional
the last line in that script performs a quick reboot, which retains temp-root and hopefully clears the DNS caches if you are still seeing ads pop up.
- - - - -
[UPDATE 11/03/2010]
I added the scripts in a zip file attached.
[update 11/04/2010]
if you dont want to manually update, you can just add the wget function into the installation script shown below. This will download the latest ad block updates at start-up, so you will not need to manually update later.
## adblock.sh ##
Code:
wget http://209.68.48.119/winhelp2002/hosts.txt -O /data/data/hosts
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -o remount,ro /dev/block/mmcblk0p25 /system
for this method, just place the same info in visionary.sh:
##visionary.sh##
Code:
sh /sdcard/gscript/adblock.sh
busybox killall system_server
replace the location to where you end up putting adblock.sh.
working example files are attached.
- - - - -
please note that you can change some of these steps to fit what other items you have running at startup.
if you're able to find a better method to perform this, please let me know! I was unable to run these commands directly within visionary.sh, so i had to make these links.
Thanks!
credits go to "Microsoft MVPs" for maintaining the HOSTS ad blocking file, delta_foxtrot2 who discovered and made the AdFree app
Nice write up, I finally got it working using root explorer and doing the steps manually, but was too lazy to script it haha, good work though
Upload the script file for us
Sent from my T-Mobile G2 using XDA App
Dalamak said:
Upload the script file for us
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
done. check the first post.
you can also be sporty and use the wget function at startup too.
For those of you who have a problem with visonary.sh locking your phone up.
Here is a gscript version.
Code:
# Overclock the CPU
insmod /data/local/vision_oc.ko pll2_l_val=73
insmod /data/local/tun.ko
# No Ads thanks XDA
rm /data/data/hosts
wget http://209.68.48.119/winhelp2002/hosts.txt -O /data/data/hosts
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -o remount,ro /dev/block/mmcblk0p25 /system
Does this actually work? I've tried hot-rebooting the phone (retaining root), and I still get ads. How does this differ from using visionary, running ad free, and hot booting?
The problem I'm seeing is that it doesn't seem like a hot reboot clears the DNS cache.
dyndragon said:
Does this actually work? I've tried hot-rebooting the phone (retaining root), and I still get ads. How does this differ from using visionary, running ad free, and hot booting?
The problem I'm seeing is that it doesn't seem like a hot reboot clears the DNS cache.
Click to expand...
Click to collapse
it sometimes block ads, sometimes does not. one, you might have to clear the caches in the apps you use as well. and two, some ads (presumably newer) arent blocked in the hosts file either.
this is not different than using adfree at all. it uses the same hosts file and same symlink technique for htc phones. i just tried to make it work automated on startup.
works here.
update
updated original post with a newer "self-healing" start up script, which will automate the entire process after running visionary root.
How come in the script you delete /etc/hosts but symlink to /system/etc/hosts ? Excuse my ignorance
you cant symlink a file that already exists, so i had to delete it. You can also just copy /data/data/hosts to /system/etc (or /etc) but it doesnt always work for some reason even though its mounted rw... this method seems to be flawless, plus you can update /data without issues and always have the latest copy there.
So does this block ads in apps? If so, it doesn't seem to block the ads that take up an entire screen (where you have to click 'skip' to move on), but seems to block the smaller ads from my brief trial period with it so far.
sorry but where exactly is visionary.sh? do i have to create it myself or does it exist somewhere after a temp-root?
ajk1311 said:
sorry but where exactly is visionary.sh? do i have to create it myself or does it exist somewhere after a temp-root?
Click to expand...
Click to collapse
You create the visionary.sh script in /data/local/
It runs automatically when you use the visionary app (located in market). Those this app is now outdated since permaroot is out.
yes. this is unneccessary if you used the new root method. the adfree app is free and does the same thing.
Sent from my T-Mobile G2 using XDA App
minotauri said:
yes. this is unneccessary if you used the new root method. the adfree app is free and does the same thing.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Or you could say that app is useless since this does the same thing
Lol, either way I like this better and I thank you for providing it!
lol. ya. but the app came first. this is just an appfree version of adfree. it still works with perm root. you just need to do the symlink once and then run the wget command when you want to update a new hosts file which is updated weekly or so.
Sent from my T-Mobile G2 using XDA App
I have been unable to get adfree to work. Still get ads in all my apps. Anyone else having this issue?
yo
since now we have perm root can you make a permanent script rather than doing visionary and scripts?
adfree from market
Adfree from the market works great with perm root. D-load from market. Open the app. Click install at the top and reboot phone. Ad's should now be blocked from apps. Angry birds with no ads!! Sweetness!!!
I have managed to get CIFS working on stock Nexus 10.
It's quite a bit more problematic on the Nexus 10 than normal.
There are 2 main issues to deal with. Newer versions of the Linux kernel require a UNC variable to be passed to them and the current version of busybox doesn't do this. There is a patch out. I have extracted the patched busybox binary from craigacomez's AOSP Nexus 10 rom.
(Check it out here: http://forum.xda-developers.com/showthread.php?t=1998585 ). Otherwise it should work on the stock mount command if you specify the unc= mount option with the share.
The other issue is the multiuser stuff. If you execute the mount command from inside Terminal Emulator (or a script program) it looks like it mounts ok and you can 'ls' in the directory but it doesn't work for Android apps, they just see an empty directory but if you do it via a 'adb shell' it works fine in Android apps. My theory is ADB is outside of the multiuser stuff. adb actually ships on the device.
1) Unlock bootloader (fastboot oem unlock)
2) Flash recovery adb flash recovery whatever.img
3) Root device (flash CWM-SuperSU-0.98.zip)
4) Install BusyBox (from the market)
5) Copy md4.ko and cifs.ko to device. The files can go anywhere you like. In this example I will just use the root of the sdcard. Some people like them in /system/modules or /system/lib/modules
6) busybox mount -o rw,remount /
7) adb shell
8) Override /system/bin/busybox with the patched version (maybe move it first so it's backed up).
9) insmod /sdcard/md4.ko
10) insmod /sdcard/cifs.ko
11) busybox mount -t cifs -o username=MYUSER,password=MYPASS,unc=\\\\192.168.1.1\\storage //192.168.1.1/storage /data/media/0/cifs/Storage
You will need to manually preform the last 3 commands each time you reboot the device from a adb shell.
NOTE: You can probably get rid of the -o flags completely. In theory the patched version of busybox makes the UNC bit redundant. Possibly you can use the stock busybox with the UNC flag and avoid using the patched one totally. I have just included it to be sure.
Make sure you type 'busybox mount' not 'mount', by default they are different binaries. Otherwise you can remove the /system/bin/mount command and make a new one linking /system/bin/mount to /system/bin/busybox.
Possibly there is some way to get the mount working in the multiuser environment without requiring busybox. If you figure it out please tell ☺
Some threads on the issue:
http://forum.xda-developers.com/showthread.php?p=34397868#post34397868
http://forum.xda-developers.com/showthread.php?t=733490&page=6
http://www.mail-archive.com/[email protected]/msg17650.html
The modules are for 3.4.5-g4e6298b.
EDIT: I added nls_utf8.ko by request
EDIT2: Since adb comes on the device, it is possible to use it to connect to local host:
1) Install cifs modules to /system/lib/modules
2) Install Script Manager from the play store
3) Copy script to device
4) Start SManager
5) Find your script and open it.
6) Tick the su box
7) Hit save
8) Goto home sccreen
9) Add a 'SMShortcuts' widget to your home screen
10) "Add one script shortcut"
11) Choose your script
12) Optionally use this pretty icon ☺
13) Give it a nice name like "Mount Shares"
Here is a shell script...
Code:
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
EDIT3: Added usbserial.ko, option.ko and usb_wwan.ko
EDIT4: Some users have reported that the need to modify the script to get it working with their version of SU.
EDIT5: I have uploaded modules for 4.2.2, kernel 3.4.5-gaf9c307 but I haven't actually tested them myself (still on 4.2.1). Apparently the adb loophole has also been patched but it is possible to reenable it by putting a RSA key onto the device. Check out this set of instructions here.
EDIT6: I have updated to 4.2.2 on my Nexus 10 and can confirm the new modules work.
You must setup the adbkey or you will get a "device: offline" message. By default adb when adb first runs it tries to create the keys in the $HOME dir which is /data/.android, but the data directory isn't accessible by the 'shell' user.
I got it working simply by setting the HOME variable to /sdcard and restarting the adb server in the script then Android popped up a query (I have update the script above).
IMPORTANT: The Android Media scanner recursively scans folders for media to add the the database so it shows up in programs like Google Music. On large shares this can be a long process and use heaps of battery life. To prevent this add a blank file with the name ".nomedia" to the root of your mount points (or each individual share if you aren't used 1 folder for all your mounts). This will stop music showing up in programs though.
If you find that the device stops responding (the launcher might work but apps fail to load) or you get reboots (often after the previous bug) this is probably due to a bad wifi connection.
Is it posible to make a CWM flash file?
Great
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
alias_neo said:
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
Click to expand...
Click to collapse
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
craigacgomez said:
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
Click to expand...
Click to collapse
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Although I don't have nexus 10, I am having the similar mounting issue on my nexus 7 until I saw this post.
Advise about "adb shell" really helps me resolve the multiuser issue.
Thanks for sharing.
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
H3g3m0n said:
1) Unlock bootloader (adb oem unlock)
Click to expand...
Click to collapse
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
momulah said:
Is it posible to make a CWM flash file?
Click to expand...
Click to collapse
Not a high priority right now as currently you need to do the manual adb shell stuff by hand to get things mounted, a little extra setup work isn't a huge difference.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
Are you mounting in a 'adb shell' or locally in something like terminal emulator? My OTG cable won't be here for a while so I can't really test myself.
weasal said:
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
Click to expand...
Click to collapse
Posted, haven't tested it but it seemed to insmod fine.
espionage724 said:
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
Click to expand...
Click to collapse
Yeh typoed, i'll fix that now.
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
I've been working on getting OTG support natively in my AOSP based custom ROM and I have had some success... check out my ROM for details
H3g3m0n said:
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
Click to expand...
Click to collapse
Just wanted to thank H3g3m0n as I was able to successfully mount over adb. Also came up with a workaround to bypass connecting to a PC, grabbed the arm fastboot binary from this thread and installed it on my nexus 7. Used it to connect wireless adb on the 10 and ran the mount commands on the 7.
H3g3m0n said:
Posted, haven't tested it but it seemed to insmod fine.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
You might find my posts #156 and #162 at http://forum.xda-developers.com/showthread.php?t=1781411&page=17 helpful.
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
spdwiz18 said:
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Loadable_kernel_module
craigacgomez said:
http://en.wikipedia.org/wiki/Loadable_kernel_module
Click to expand...
Click to collapse
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
These modules are needed to enable support for CIFS (Windows share) mounts...
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
Basically you can setup a shared folder from a remote computer. It allows you to have files on another system accessible as if it was part of the internal storage in the device.
Just found out that Android ships with the adb binary on the device itself (after crosscompiling it myself :/, oh well the experience was useful).
It should be possible to setup a script to start the adb server, connect to the localhost and execute the mount without too much difficulty.
Ok, added a script and instructions to the front page for simple on tablet mounting.
Hello all.
I'm running my FireTV as an entertainment system. It's rooted with Kodi, Mobdro, RetroArch, ePSXe w/ Sixaxis PS3 as controller etc.
Since the FTV only has 8GB of local storage, I was wondering if there's a way to mount a samba share into a local directory so I can load emulator games without transferring them. Majority of the emulators only scan ROMs / ISOs etc on local directories.
Unfortunately, apps like cifsmanager and mount manager are broken since android 4.3 I think.
Thanks in advance.
Maybe this might be helpful:
http://forum.xda-developers.com/fire-tv/general/run-script-firetv-boot-t2986158
This works for me:
Code:
busybox mount -t cifs //my.ip.address/my.share /sdcard/somedir -o username=guest
jocala said:
This works for me:
Code:
busybox mount -t cifs //my.ip.address/my.share /sdcard/somedir -o username=guest
Click to expand...
Click to collapse
Hello there.
Thanks for the help. But do you mind answering a couple of Qs because I'm a filthy nub when it comes to this.
1. Where do I run this command? Do I connect to my FTV using adb and just type this in?
2. How would this work if my Samba share has spaces on it?
3. Do I run this everytime I reboot my FTV?
Thanks again
Squalll13 said:
Hello there.
Thanks for the help. But do you mind answering a couple of Qs because I'm a filthy nub when it comes to this.
1. Where do I run this command? Do I connect to my FTV using adb and just type this in?
2. How would this work if my Samba share has spaces on it?
3. Do I run this everytime I reboot my FTV?
Thanks again
Click to expand...
Click to collapse
1. As posted, it would be run from the command line, from a root prompt. I use busybox, so you need that as well for my method.
2. I stay away from directories with spaces, but it may work with quotes, idk, haven't tested. It works with embedded spaces if they are inclosed in quotes: e.g:
Code:
busybox mount -t cifs "//192.168.1.200/media/my folder" /sdcard/cifs -o username=guest
3. Easiest thing to do would be to put it into a script that runs at boot. That's the approach I'm taking with my program adbFire. I'm testing this functionality now.
oops.... guess that was already answered. Anyhow, can't leave text field blank so; Yeah this works great. I got mine all set up with Advanced Launcher kodi addon. Tested with a few emulators and ISOs load near instantly
Thanks for the replies. Though I noticed something peculiar and I would like some insight.
I noticed that after I haven't used the FireTV for a while. Maybe 24 hours. The mounted folder kinda "disappears" for a bit but come back. For example, I use ES File Explorer and go to /mnt/obb/ and it will just keep "Loading" until I just press back. Same thing when I used adb shell, cd to /mnt/obb/ and use ls. It just stays there until I force exit. But after a waiting around a bit like 10 mins or so, the mounted folder shows up no problem.
It kinda feels like you need to ping /access it or something, fail, wait a bit then it shows up.
I hope what I said isn't too confusing. If it was I apologize.