Related
Hi,
I've been struggling with OpenVPN for quite some time now, but have finally got it connecting using DeFrost 2.0d. The joy ends there as no pages load for me. Have googled, and googled some more to figure out the issue.
I thought it could be DNS related or perhaps something mentioned in this thread with a fix in this post ?
"
wraithdu posted on 28th June 2010, 04:20 PM
I had the same problem, and it's due to the built in versions of ifconfig and route I think. I did this:
1) installed busybox 1.15.3 to /system/xbin and installed the links (busybox --install .)
2) reboot into recovery
3) mount /system and adb shell:
# cd /system/bin
mv ifconfig ifconfigoff
mv route routeoff
ln -s /system/xbin/busybox ./ifconfig
ln -s /system/xbin/busybox ./route
4) reboot
This creates the busybox ifconfig and route symlinks in /system/bin. After this, OpenVPN Settings works perfectly. Since OpenVPN uses hardcoded paths, this is the only workaround I can think of."
Related to ifconfig and route?
Anyone with any tips for me - much appreciated!
Cheers
(Sorry - can't post link to thread as new user - in Droid Incredible Android Development)
semi-fixed...
works fine over wifi...the problem above over 3G...connects fine but doesn't browse anything. very strange. could my provider be blocking vpn?
anybody on Hi/KPN in the netherlands and have this working over 3G? have seen reports of the same problem quite allot, fine over wifi but not over 3g.
In my case problem was that Desire didn't acquire IP address from DHCP. The same config file that worked on my laptop didn't work on my phone. VPN connected properly by could not open any page from my local network.
After I've added ifconfig line in ovpn config file - it started to work.
could you show me an example of your config please?
Hi,
openvpn is up and running.
Install busybox via busybox-Installer (Market). Then install Openvpn via Openvpn-Installer (Market). I dont know if Openvpn-Installer is needed, as we are replacing the binary with another file - but as it takes care of dependencies just install it
Use tun.ko from there:
xxx.android-hilfe.de/samsung-galaxy-tab-forum/51007-openvpn-tun-ko-unionfs-ko.html
(replace the xxx with www)
Binary from here: (OpenVPN Installer won't work - its not able to recognize push options)
github.com/downloads/fries/android-external-openvpn/openvpn-static-2.1.1.bz2
Finally you have to provide the busybox-ifconfig in /system/xbin/bb/ifconfig and busybox-route in /system/xbin/bb/route (ln -s /system/bin/busybox /system/xbin/bb/ifconfig ...)
cheers
patrick
Can you give any hint how to install the additional binaries? Even with a rooted Tab and a terminal, I dot not get this working.
Sent from my GT-P1000 using Tapatalk
hi
just run openvpn installer from the market
I tried and got the connection established. But in opposite to my Desire, traffic is not routed that way.
Also, there is no /dev/tun
Addendum: Got it running, beside that I am using tap, doing a reinstall after having created the a.m. symlinks for busyboy, adding some push options on the server to force the routing did the trick (they were not required on my Desire).
I used the tun.ko module for the VPN Connections app and got it working great... except when I disable the VPN connection, it doesn't reset the dns servers to the values that where there before.
I don't believe it's the application since the same version on my Nexus One works correctly. If I turn off the data then turn it back on, I get my data back. I believe it to be the tun.ko not being written to reset the dns entries.
I think I could kiss someone, I now have working cisco vpn
How do we make the tun.ko module stay after a reboot? Mine disappeared from /modules/ when I restarted my tab? I copied it with root explorer.
Also if we can get it to stick will I have to run these commands each time?
insmod /modules/tun.ko
ln -s /system/bin/busybox/system/xbins/bb/ route
ln -s /system/bin/busybox/system/xbins/bb/ ifconfig
Hi, i am not getting this to work, is there any thing i am missing? What i did:
1. Rooted device and installed busybox
2. copying the tun.ko from the german site to /modules after remounting to r/w.
3. Running those three commands from previous post in terminal
4. Installing vpnc 0.99 and configuring connection
5. Connect
still get failed to connect.
any tips please?
Sent from my GT-P1000 using XDA App
trondjl said:
Hi, i am not getting this to work, is there any thing i am missing? What i did:
1. Rooted device and installed busybox
2. copying the tun.ko from the german site to /modules after remounting to r/w.
3. Running those three commands from previous post in terminal
4. Installing vpnc 0.99 and configuring connection
5. Connect
still get failed to connect.
any tips please?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I believe that's exactly what I did. Were all the commands successful?
works now.
I rebooted and reinstalled vpnc and busybox and recopied and reissued commands. Something must have been hanging from all my testing.
Tanks!
This is so great! Now I'm online with Sip, xmpp and RDP with work!
I know, get a life
Sent from my GT-P1000 using XDA App
I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.
Yes, it works. Excellent!
Sent from my GT-P1000 using XDA App
sorry for noob question as i dont know that much about open vpn
i know its a virtual private network, and some ppl in my country offering a cheaper internet connection through them
what did this one do exactly?
Cisco vpn ftw
This is great! After reading everything and getting everything done I can connect through our Cisco VPN.
Question
What does this do that the Tabs built in VPN doesnt?
How can I use terminal emulator to run the two ln -s commands? I guess I need some prior commands to enable r/w to system?
I bought Better Terminal Emulator Pro in the Market to do this.
This is how I did it:
1. Install busybox from the Market into /system/bin,
2. Install root-explorer (to get r/w access to /system/xbin),
3. Create /system/xbin/bb,
4. Create symbolic links in /system/xbin/bb to busybox with the names ifconfig and route:
ln -s /system/bin/busybox /system/xbin/bb/route
ln -s /system/bin/busybox /system/xbin/bb/ifconfig
5. Copy tun.ko into /system/xbin with root-explorer,
6. Install OpenVPN from the Market into /system/xbin and set the paths to route/ifconfig to /system/xbin/bb,
7. Install OpenVPN Settings from the Market,
8. Configured to activate the TUN module via Menu / Advanced with insmod in path /system/xbin/tun.ko and to activate "Load tun kernel module"
9. Copied my existing and working OpenVPN-settings to the memory card and finally
10. Set the path to the OpenVPN configuration and to the OpenVPN binary.
After this, the OpenVPN connection could be established the data was rerouted via that connection.
@alias_neo
The internal Android functions do not support OpenVPN which can be quite easily installed on a Linux root server to establish a secure connection to that server. Setting the firewall rules on that server properly, the whole traffic can virtually enter the internet via the server and systems inbetween the Tab and the server cannot see what's going on anymore. So even an open WLAN hotspot can be safely used as well as all monitoring/logging/recording on forwarding systems sees only an encrypted connection.
Also OpenVPN is in my eyes more secure than a simple username/password encrypted connection (as PPTP offers). So, the secret to encrypt the connection is better protected as with PPTP.
If a VPN provider is used to tunnel the traffic into the internet (to hide it from the systems inbetween when there is no own server available), the encryption method of the VPN provider is relevant. For example, SwissVPN only offers PPTP or OpenVPN.
ipaqkiller said:
I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.
Click to expand...
Click to collapse
I don't know if' I'm missing something, but I can't get the module to automatically load on a reboot. lsmod doesn't show tun.ko in the list. I have to issue insmod /system/lib/modules/tun.ko on each startup.
EDIT: Think I've sussed it, will post my details later for anyone who wishes to get this setup for cisco only without installing the openvpn installer.
ritdaw said:
I don't know if' I'm missing something, but I can't get the module to automatically load on a reboot. lsmod doesn't show tun.ko in the list. I have to issue insmod /system/lib/modules/tun.ko on each startup.
Click to expand...
Click to collapse
That's why I use the OpenVPN Settings app from the Market. It allows to activate the module with insmod when OpenVPN is started as this obviously cannot be done by the system automatically.
ipaqkiller said:
I had to copy tun.ko to /system/lib/modules. I did have to create that directory but when I did, it was loaded every time.
You can make sure by using the lsmod command in the terminal emulator.
Click to expand...
Click to collapse
akxak said:
That's why I use the OpenVPN Settings app from the Market. It allows to activate the module with insmod when OpenVPN is started as this obviously cannot be done by the system automatically.
Click to expand...
Click to collapse
Worked that out in the end, I thought it was only specific to OpenVPN connections.
Nevermind...?
Hello all,
I'd like to preface this by saying this is a Cricket phone. Even if you know nothing about Cricket you may be able to help, so please read on. Note: because it's a Cricket phone I'm using autostart and a script to connect to the internet.
So a few days ago I messed up my phone to the point where it wouldn't boot. After that I had to learn how to flash (I didn't know before) and so I'm very new to all of this.
Here's what I've done:
- I flashed to the official 2.2, EC05
- I restored my data from my old nandroid backup
- I edited my phone's PRL and then went into QPST and changed the info so it will connect to the internet
- I copied autostart.sh to /data/opt/ and made sure the /opt/ director is 777 and the autostart.sh is 755
- I copied u2nl to /system/bin/ and made sure it was 755
I don't really have any questions about any of that because after I did this and restarted the internet was working fine. It worked fine for a few hours, then I had to restart my phone and now all of the sudden it's not working.
Autostart is launching when the phone starts, and it's being given superuser permissions, but the internet is not working.
- I can see the 3g symbol at the top of my phone, and arrows move in both directions
I think it might be an app that I've got installed that's blocking connectivity, however I've been disabling them and I'm still not getting anywhere. Does anyone have any clue why this could be happening?
Just wanted to edit and also ask: if it is an app blocking my connectivity, why did it work at all? The first time I restarted after granting autostart superuser ability, the internet worked fine for hours and hours. It was only after I restarted the phone again that the internet went away.
Thanks.
Maybe its with autostart app. Maybe something got changed when your phone booted up and now its affecting your internet. Is anything working that involves a data connection?
Sent From My Evo Killer!
musclehead84 said:
Maybe its with autostart app. Maybe something got changed when your phone booted up and now its affecting your internet. Is anything working that involves a data connection?
Sent From My Evo Killer!
Click to expand...
Click to collapse
Nothing that involves data is working, but everything (internet and data) was working when I first restarted the phone.
After playing with it all day I thought the AutoKiller app might have been causing the problems, but then this evening it got even worse. Initially my AutoStart app would run on boot, but the internet wouldn't work. Now the AutoStart app isn't even running on boot, and I'm 100% sure I've got it installed. I removed all apps that had anything to do with apps that run on boot or data control, and it still won't run on boot.
I don't really understand why but this AutoStart app will not consistently AutoStart anymore, and even when it did a few hours ago the data connection would only work on the first restart, and then it would AutoStart but the connection wouldn't work.
Does anyone have any idea? It's a pain in the butt to have a smartphone that doesn't do anything except text/calls
Maybe try to Clear you Cache in CWM. I had to do that once because I lost data.
Maybe even try doing a Fix Permissions in CWM.
hopefully it is this easy. If not sorry :O
For anyone who is interested I believe I have solved the problem.
According to a few other people here on the forums the stock 2.2 does not allow Autostart to work, so it may work once or twice but will not regularly work.
I got around this by using the Locale Execute Plugin which is a plugin written for the Locale app, however it can be used independently of the Locale app (read: you do not have to buy the Locale app, you can download the Execute plugin free and use it without Locale). I used Tasker to setup an On Boot trigger, and have it running the Locale Execute Script which launches Autostart.sh and allows my internet to connect.
I noticed the internet was still acting funny and removed my Autokiller app as well as my Phone Prioritizer app (I was using this to make sure my actual phone had priority over all other apps, it was running a script every 30 minutes). The internet seems to be functioning well now.
Here is a copy of my autostart.sh file (create a file called autostart.sh and edit it with notepad, copy and paste this code then save)
Code:
#!/system/bin/sh
export PROXYHOST=wap.mycricket.com
export PROXYPORT=8080
export MMSHOST=mms.mycricket.com
export MMSPORT=80
#you shouldn't have to edit anything below this line
export PATH="$PATH:/system/bin"
until netcfg|grep -v DOWN|awk '{print $1}'|grep -v wlan|grep -v lo >/dev/null 2>&1 ; do sleep 1 ; done
export INTERFACE=`netcfg|grep -v DOWN|awk '{print $1}'|grep -v wlan|grep -v lo`
export PROXYIP=`ping -c 1 $PROXYHOST|grep PING|cut -d\) -f1|cut -d\( -f2`
export MMSIP=`ping -c 1 $MMSHOST|grep PING|cut -d\) -f1|cut -d\( -f2`
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F
iptables -t nat -F
iptables -X
iptables -t nat -A OUTPUT -o $INTERFACE -p 6 -d $MMSIP --dport $MMSPORT -j DNAT --to-destination $MMSIP:$MMSPORT
#iptables -t nat -A OUTPUT -o $INTERFACE -p 6 --dport 80 -j DNAT --to-destination $PROXYIP:$PROXYPORT
iptables -t nat -A OUTPUT -o $INTERFACE -p 6 ! -d $PROXYIP ! --dport $PROXYPORT -j REDIRECT --to-port 1025
u2nl $PROXYIP $PROXYPORT 127.0.0.1 1025 >/dev/null 2>&1 &
sh -c "sleep 5;kill `ps|grep nk.bla.android.autostart|grep -v grep|awk '{print $2}'`" >/dev/null 2>&1 &
exit 0
Here's a step-by-step breakdown of what I did:
I used:
Tasker (paid app)
Locale Execute Plugin (free app - (link)(link2))
Root Explorer (paid app)
Patience
- Created autostart.sh file and copied it to my SD card
- Copied u2nl file to the SD card (link - download the token419_cricket_data_setup_1.2.zip, it's located in system/bin/ within that zip)
- Opened the "Root Explorer" app and copied the Autostart.sh file, then browsed to /data/ and created a folder called "opt".
- Pasted autostart.sh in /data/opt/ and made sure it was 755 (long press then go to permissions and check User: read/write/execute, Group: read/execute, Others: read/execute).
- Copied u2nl from the SD card and pasted it to /system/bin/ on my phone, made sure it also had 755 permissions
- Downloaded Locale Execute Plugin (link)(link2)
(note: since your phone is not connected to the internet, connect to a wifi network to download this app from the market)
- Launched Tasker and created a new rule > event > system > device boot
- Added an action > plugin > execute
- Entered "@!/data/opt/autostart.sh" and saved (the @ tells it to not send you a popup when it runs, the ! gives it superuser permissions)
- Saved by pushing the back arrow on my phone's touchscreen
- Clicked "apply"
- Rebooted, and clicked "allow" when Locale Execute Plugin requested superuser permissions
That's it, my internet started working after this. I had to remove those other previously mentioned apps, but that was just me. If your internet isn't working after doing this, first make sure you did everything right. If it's still not working try to think of any apps you have that might be overwriting the autostart.sh file's settings. If worst comes to worst, start uninstalling apps until it works again. Reboots will be required after you uninstall an app.
Hopefully this helps someone out there.
Glad u got it man.
Sent From My Evo Killer!
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.
Did anyone successfully install debian kit on the galaxy note 10.1 (2014) ?
I tried,
sh /storage/emulated/0/debian-kit-1-6.shar
unpacks properly, but then nothing happens. A wizard is supposed to start.
I tried both 1-6.shar from Doviak, and 1-5.shar from sven-ola
I did the following. Start with unrooted device. Accept KK OTA upgrade. Now
I have SM-P600 with Android 4.4.2. Root with CF. This fails.
Flash openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar with Odin. Then boot into TWRP and
install UPDATE-SuperSU-v1.94.zip. Now some apps ask for root access and it seems to be
granted; installed sdfix, and at least one app (aplinequest) that could not write after
the KK upgrade can now write to extsdcard.
Installed Debian Kit app. All green checks, except red Xs for "Kernel modules supported"
and "Valid 'su' command found". But I know su is working. (I think there was a red X by Debian
Kit already unpacked)
Transfer debian-kit-1-6.shar to device. I follow instructions, Install connectbot. Give 'su'.
Run sh /storage/emulated/0/debian-kit-1-6.shar
Get error messages (I didnt record them), such as md5sum not found, and
a couple of other binaries not found. I give echo $PATH and then look for these binaries
in my path. They are not there. So I install BusyBox Free. Run the shar file again. I
get a list of files extracted, but then nothing happens. Now I see that debian kit wants
to use its own busybox and I didnt need to install busybox, but debian kit did not work
in any case.
I try to run /data/local/deb/autorun with sh autorun. Exits with "Unsupported CPU or architecture"
Investigate and find shell var CPU is set correctly to "armel" on first past, but when the script
runs again with exec, CPU is ''. So I hardcode CPU=armel. Then I can get a little further.
And so on and so on, hardcoding CPU in all the scripts. Trying to get the scripts to see the
correct binaries, etc. Now I have a diskimage installed, can't go forward and can't uninstall.
If anyone can shed some light....
update
Deleted everything and started over. Using adb shell. I notice
that the installer says
Included busybox failed.
and tries to use system tar, sed, etc, which it cannot find.
However, If I put #!/system/bin/sh at the top of debian-kit-1-5.shar
And run ./debian-kit-1-5.shar rather than sh ./debian-kit-1-5.shar,
then the script runs for quite a while and extracts a lot of files.
It fails eventually with
ash: id: Permission denied
In fact, from the adb shell I get
126|[email protected]:/data/local # id
uid=0(root) gid=0(root) context=u:r:init:s0
[email protected]:/data/local # ./deb/armel/busybox ash -c "id"
ash: id: Permission denied
126|[email protected]:/data/local # ./deb/armel/busybox ash -c "/system/bin/id"
ash: /system/bin/id: Permission denied
More Update
It seems that in some cases the user 'shell' has permission to do something, but 'root' does not.
One thing stopping the debian kit install process is that root running a shell located under /data cannot run any executables via
passing a string on the command line. They can run commands interactively (maybe because the command
line uses exec ?). But the user 'shell' can run executables this way. E.g. I copied /system/bin/mksh to the /data partition.
[email protected]:/ $ su
[email protected]:/ # /data/local/bin/mksh -c "id"
/data/local/bin/mksh: id: Permission denied
1|[email protected]:/ # /system/bin/mksh -c "id"
uid=0(root) gid=0(root) context=u:r:init_shell:s0
[email protected]:/ # su shell
[email protected]:/ $ /data/local/bin/mksh -c "id"
uid=2000(shell) gid=2000(shell) context=u:r:init:s0
There are a few posts scattered around other forums mentioning the same problem when trying to
install debian kit, but no responses even recognized that there was a problem.
The solution was to install an selinux permissive kernel. Then installation
went normally.
I think I can help.
injola said:
Did anyone successfully install debian kit on the galaxy note 10.1 (2014) ?
I tried,
sh /storage/emulated/0/debian-kit-1-6.shar
unpacks properly, but then nothing happens. A wizard is supposed to start.
I tried both 1-6.shar from Doviak, and 1-5.shar from sven-ola
I did the following. Start with unrooted device. Accept KK OTA upgrade. Now
I have SM-P600 with Android 4.4.2. Root with CF. This fails.
Flash openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar with Odin. Then boot into TWRP and
install UPDATE-SuperSU-v1.94.zip. Now some apps ask for root access and it seems to be
granted; installed sdfix, and at least one app (aplinequest) that could not write after
the KK upgrade can now write to extsdcard.
Installed Debian Kit app. All green checks, except red Xs for "Kernel modules supported"
and "Valid 'su' command found". But I know su is working. (I think there was a red X by Debian
Kit already unpacked)
Transfer debian-kit-1-6.shar to device. I follow instructions, Install connectbot. Give 'su'.
Run sh /storage/emulated/0/debian-kit-1-6.shar
Get error messages (I didnt record them), such as md5sum not found, and
a couple of other binaries not found. I give echo $PATH and then look for these binaries
in my path. They are not there. So I install BusyBox Free. Run the shar file again. I
get a list of files extracted, but then nothing happens. Now I see that debian kit wants
to use its own busybox and I didnt need to install busybox, but debian kit did not work
in any case.
I try to run /data/local/deb/autorun with sh autorun. Exits with "Unsupported CPU or architecture"
Investigate and find shell var CPU is set correctly to "armel" on first past, but when the script
runs again with exec, CPU is ''. So I hardcode CPU=armel. Then I can get a little further.
And so on and so on, hardcoding CPU in all the scripts. Trying to get the scripts to see the
correct binaries, etc. Now I have a diskimage installed, can't go forward and can't uninstall.
If anyone can shed some light....
Click to expand...
Click to collapse
I have the same tablet and I tried to answer you several times but when I give exact instructions they don't let my reply get to the thread for some reason. So I'll have to be less specific, sorry. Anyway. I rooted with an omnirom based setup. 412. Homemade. Once you get the debian-kit-1-6-testing.jpeg and you've unloaded it to you your root directory try:
#sh /data/local/deb/mk-debian -i
Follow the usage correctly and until your done testing leave:
-h
At the end of the script. But be sure to set it to armel and 2047 and wheezy and set the mirror to:
deb. .org/dists/wheezy/ main contrib non-free
Kali
catch all the protools and for the gpg licence use google search my username KeizerPaPa and I'll give you the gpg on my + account. Goodluck. ]
---------- Post added at 06:40 PM ---------- Previous post was at 06:28 PM ----------
KeizerPaPa said:
I have the same tablet and I tried to answer you several times but when I give exact instructions they don't let my reply get to the thread for some reason. So I'll have to be less specific, sorry. Anyway. I rooted with an omnirom based setup. 412. Homemade. Once you get the debian-kit-1-6-testing.jpeg and you've unloaded it to you your root directory try:
#sh /data/local/deb/mk-debian -i
Follow the usage correctly and until your done testing leave:
-h
At the end of the script. But be sure to set it to armel and 2047 and wheezy and set the mirror to:
deb http .org/dists/wheezy/ main contrib non-free
Kali
catch all the protools and for the gpg licence use google search my username KeizerPaPa and I'll give you the gpg on my + account. Goodluck. ]
Click to expand...
Click to collapse
Make sure you piece the above together correctly, they wouldnt let me type it all together. Thats deb http: //http
Then .kali then .org/dists....... have fun. If ya get stuck on the gpg search me and ask. KeizerPaPa
A reason why mine failed at first was because "Debian kit" is set to resolve ip addresses using "only" your Primary DNS Server (DNS 1). When I finally pinged my Primary DNS server, I found it was not functional. My Secondary DNS server (DNS 2) was functional (this also explains why my internet was slower than it should have been while browsing the internet)
I changed my Primary DNS server by
1) going into the WIFI settings
2) long-pressing on the WIFI I was connected to
3) choosing "Mofify..."
4) checking the "Show advanced..." option
5) changing from "DHCP" to "Static"
6) entering a functional DNS server (such as 8.8.4.4) for "DNS 1"
- Hyp