Has anyone found or created a working tun.ko for the A500? I realize it's early to be asking this, but it's something I ultimately need.
Dmesg says the version number should be:
2.6.36.3-00001-g9b3ce2b SMP preempt mod_unload ARMv7
+1 looking for the same. Xoom tun.ko won't install on the A500.
FYI, thor2002ro posted one on the dev forum:
http://forum.xda-developers.com/showthread.php?t=1058713
Just download the one that matches your specific Kernel (look in Settings - About tablet to see what you have running.)
On another note, I found that the default BusyBox and OpenVPN Installer's on the Market wouldn't quite work. Busybox installs at /system/xbin/ and I told OpenVPN to look for it there, but it REALLY looks for it at /system/xbin/bb/ so I created that directory, created symlinks for "route" and "ifconfig" in that directory pointing back to the /system/xbin/busybox executable.
For those not in the Linux know, at the adb shell you'd do:
su
mkdir /system/xbin/bb
ln -s /system/xbin/busybox /system/xbin/bb/route
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
exit
exit
Related
i read here
http://android-dls.com/wiki/index.php?title=Installing_Debian
you can run debian on android whit installing it.
and dont loos your droid
first isseu i got. chmodding the thing
download and push debian to /sdcard/debian
Code:
cd /sdcard/debian
su
chmod 4755 *
Code:
# su
su
su: access granted, courtesy of www.magicandroidapps.com
# chmod 4755 /sdcard/debian/*
chmod 4755 /sdcard/debian/*
Unable to chmod /sdcard/debian/bootdeb: Operation not permitted
#
than whitout bootdeb is chmodded i tried the installer.sh
Code:
cd /sdcard/debian as root
sh ./installer.sh
it just say's
Code:
# sh ./installer.sh
sh ./installer.sh
su: access granted, courtesy of www.magicandroidapps.com
#
so ?
Code:
# exit
Code:
# exit
exit
modprobe: not found
clear: not found
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
clear: not found
cp: not found
cp: not found
cp: not found
cp: not found
cp: not found
Unable to chmod bootdeb: Operation not permitted
clear: not found
VERSION 2.1
Custom Debian Bootloader is now installed! Quick huh?
This process does NO damage to your Android underlying OS!
Courtesy of http://www.androidfanatic.com
Installer by Mark Walker (ghostwalker)
To enter the Debian Linux console just type 'bootdeb'
PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST
boot'.
??
Code:
# rm
rm
rm [-rR] <target>
availible
Code:
cp: not found
not availible.. Busybox availible only cp but the debian installer does not support the busybox way.
Code:
# busybox cp
busybox cp
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call binary
Usage: cp [OPTION]... SOURCE DEST
enz.
Code:
#modprobe
not found
Code:
# busybox modprobe -h
busybox modprobe -h
modprobe: invalid option -- h
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call bin
Usage: modprobe [-knqrsv] MODULE [symbol=value ...]
what to do to get this running?
Troubleshooting
Troubleshooting
If chmod 4755 * gives you an error stating that you do not have permissions, close Terminal Emulator and run su again, this time when SuperUserWhitelist asks for if you should give Terminal Emulator super user permissions hit yes instead of always.
If running installer.sh tells you that installer.sh could not be found, type su, followed by sh installer.sh
what whitelist?
I'm getting the same errors as u are. I belive the whitelist sugestion is only for those who have the app installed. The problem must lie somewhere else.
Have you done my busybox install (somewhere in this forum)? Looks like if you use stock ultities you don't have requirements...
bootdev.sh
keatonreckard said:
or you can simply rename the attached bootdev.sh.txt to bootdev.sh and put it in your debian folder and its good as new
Click to expand...
Click to collapse
these posts or were is that installer??
Yah I did have busybox installed.
superuser.apk
http://androidforums.com/all-things-root-behold-2/46137-how-root-apps-working-persistent-root.html
i think this is that superuser whitlist
I have fixed the bootdeb file, but im stuck at mounting the debian image...
Did anyone make any new progress on getting debian to work?
lgstoian said:
Did anyone make any new progress on getting debian to work?
Click to expand...
Click to collapse
I haven't made much progress...
But with Fyodor's 0.4.1 ROM modprobe works but i get this error when mounting the debian image:
ioctl: LOOP_SET_FD: Device or resource busy
Click to expand...
Click to collapse
And after that the rest ****s up...
Who can write a tutorial of Debian on TATTOO?
Hi,
I've just replaced the stock toolbox with busybox provided by netarchy kernel package. Maybe there is a better way to do this, but I'm just playing with my new phone
Anyway, this is what I did:
Info
nexus model: I9023
rom: stock 2.3.4 with root permission
kernel: 2.6.35.13-netarchy-nexus-1.3.7-bfs-2.3.4
busybox version: 1.16.0 (included in netarchy kernel package)
Entering adb shell
Code:
adb shell
Inside adb shell:
Replacing toolbox with busybox
Code:
mount -o rw,remount /dev/block/mmcblk0p1 /system
busybox mv /system/bin/toolbox /system/bin/toolbox.bak
busybox ln -s /system/xbin/busybox /system/bin/toolbox
mount -o ro,remount /dev/block/mmcblk0p1 /system
Add a new command
After remounting rw /system
Code:
ln -s /system/xbin/busybox /system/xbin/COMMAND
For example:
Code:
mount -o rw,remount /dev/block/mmcblk0p1 /system
ln -s /system/xbin/busybox /system/xbin/chroot
mount -o ro,remount /dev/block/mmcblk0p1 /system
If you know a better way, tell me! Anyway I hope this could be useful
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
snandlal said:
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
Click to expand...
Click to collapse
Or just download BusyBox from Titanium Backup.
Code:
# busybox --install /system/xbin
should do the trick -- be warned, you'll get *a whole lot* of symlinks to busybox
snandlal said:
Download "busybox" by Stericson
Install busybox thru that app
Uninstall "busybox" by Stericson (busybox will stay intact)
Click to expand...
Click to collapse
Great, thanks. I've installed that busybox and it works great!
suksit said:
Code:
# busybox --install /system/xbin
should do the trick -- be warned, you'll get *a whole lot* of symlinks to busybox
Click to expand...
Click to collapse
Yes, I installed busybox in /system/xbin and it created a lot of symlinks, but it's ok because in this dir there is almost nothing.
Anyway, thanks for the tip
???
Weird! After running shell script, I can no longer stay connected on wireless for more than a couple of minutes. I think something was replaced and it shouldn't be replaced!
Any hint?
In most Android systems, the c binary stalk is installed in /system/bin and is handled by TOOLBOX.
If we install BUSYBOX with any of the apps mentioned above, it will most likely be installed in /system/xbin
So at the end we'll end up with 2 utilities handling some binaries that are clones as it show in both /system/bin and /system/xbin
and because the PATH includes both locations then wouldn't that create some complications and possible hanging/crashing of the android system ???
I was using SwiFTP to upload files, but it seemed to freeze when downloading ...
The reason is that the /system/bin/ls command on S3 returns output which is different from previous Android versions ...
The solution is to replace /system/bin/ls (which points to toolbox) to point to busybox.
Code:
cd /system/bin
mv ls ls.orig
ln -s /system/xbin/busybox ls
Make sure you have busybox installed in /system/xbin and that your /system partition is mounted read/write.
If you don't know what this is doing, please don't attempt to do it
With Android 4.2's multi-user stuff and the dreaded "0" folder, Google broke mounting of CIFS shares for good. (They basically implemented something utterly useless for my needs, and broke something I need on a daily basis.) Cyanogenmod fixed that for mounts outside the /storage hierarchy, but many apps can't go there. And with 4.2.2, Google made using adb on the device very annoying as well, which adds to problems for a workaround for mounting shares in a useful place.
So I looked around for various fixes for that issue and compiled those into one method that works perfectly well for me on a P6810 running the current PAC ROM 20130629. It should probably work for any other CM10.1 or PA3.6x-based ROM as well. A nls_utf8.ko module compiled for the Nexus 10 is included as well, which can be loaded via punchmod (at least in PAC), so you can access shares with Ümläüts in them.
Prerequisites: SManager, SMWidgets, and a working Busybox install (I use Stericson's Busybox Installer).
1.) Extract nls_utf8.ko and punchmod from the attached .zip file and put them in /system/lib/modules. You can put them in some other place as well, but my scripts need to be adjusted then. Next, give the files sufficient permissions:
Code:
chmod 644 /system/lib/modules/nls_utf8.ko
chmod 755 /system/lib/modules/punchmod
2.) Optional: if you want the module to auto-start, create a file called 00punch-nls_utf8 (or whatever you like) with the content below, put it in /etc/init.d and chmod it to 755. To check if nls-utf8 is loaded after a reboot, type lsmod in a terminal window or adb shell - it should display the module name. If punchmod auto-detection fails, read here how to get the right vermagic string for your device: http://forum.xda-developers.com/showthread.php?p=41920265#post41920265
Code:
#!/system/bin/sh
sleep 10
/system/lib/modules/punchmod /system/lib/modules/nls_utf8.ko ""
3.) Here's the script that mounts a CIFS share. Edit the settings on top and either put your correct vermagic string as well, or delete the "$VERMAGIC" part in line 22 and try your luck with auto-detection. I put some sanity checks in the script, but it might not work for all directories in /sdcard (or, /data/media/0, to call it by its 'real' name/location). If you don't want to use the nls-utf8 module, just delete lines 18-23, and iocharset=utf8 in line 67.
Name the script mount-music.sh or something, put the script wherever you like, open SManager and navigate to the script. Run the script with SU permissions. If everything goes well, it will ask you to accept an adb RSA key, and then adb mounts the share. You can also add a desktop widget for quick access to the script with SMWidgets.
Code:
#!/system/bin/sh
# Your settings here
IP="192.168.1.123"
SHARE="Music"
USER="yourusername"
PASS="yourpassword"
MOUNTPOINT="/data/media/0/cifs"
VERMAGIC="3.0.31-CM-ga034655-dirty SMP preempt mod_unload ARMv7 p2v8 "
# Load cifs (if it isn't already loaded)
if [ `lsmod | grep -o cifs` ] ; then
:
else
insmod /system/lib/modules/cifs.ko
fi
# Load nls_utf8 brute-force style (if it isn't already loaded)
if [ `lsmod | grep -o nls_utf8` ] ; then
:
else
/system/lib/modules/punchmod /system/lib/modules/nls_utf8.ko "" "$VERMAGIC"
fi
# Check if cifs $MOUNTPOINT dir exists, create it if not, give sufficient permissions
if [ -d $MOUNTPOINT ] ; then
:
else
mkdir $MOUNTPOINT
fi
chmod 755 $MOUNTPOINT
# Check if $SHARE directory is empty - if not, unmount the share
if [ "$(su root -c busybox ls -A $MOUNTPOINT/$SHARE 2> /dev/null)" == "" ] ; then
:
else
/system/xbin/busybox umount -l $MOUNTPOINT/$SHARE
fi
# Create $SHARE directory if necessary, give sufficient permissions
if [ -d $MOUNTPOINT/$SHARE ] ; then
:
else
mkdir $MOUNTPOINT/$SHARE
fi
chmod 755 $MOUNTPOINT/$SHARE
# Starting adb
adb kill-server
export HOME=/sdcard
# PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb start-server
cat /sdcard/.android/adbkey.pub >> /data/misc/adb/adb_keys
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
# Mounting share via adb
echo Mounting share via adb...
adb -s $SERIAL shell su root -c /system/xbin/busybox mount -t cifs //$IP/$SHARE $MOUNTPOINT/$SHARE -o user=$USER,pass=$PASS,iocharset=utf8,cache=none,directio,CIFSMaxBufSize=130048,rw,file_mode=0777,dir_mode=0777,uid=1015,gid=1015
# If you started adb, then stop it here for security
adb disconnect localhost
stop adbd
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port $PORT
start adbd
# Show some results
RESULT=`mount | grep $MOUNTPOINT/$SHARE`
if [ "$RESULT" = "" ] ; then
echo "FAILED! //$IP/$SHARE could not be mounted."
else
echo "SUCCESS! //$IP/$SHARE has been mounted on $MOUNTPOINT/$SHARE."
fi
echo
echo All done. You may close this script window now.
4.) This is the script to unmount the share. Name it unmount-music.sh or similar, and edit your settings at the beginning of the script. Again, run it in SManager with SU permissions, and add a desktop widget with SMWidgets if you like.
Code:
#!/system/bin/sh
# Your settings here
SHARE="Music"
MOUNTPOINT="/data/media/0/cifs"
# Check if $SHARE directory exists
if [ -d $MOUNTPOINT/$SHARE ] ; then
# Check if $SHARE directory is empty - if not, unmount the share
if [ "$(su root -c busybox ls -A $MOUNTPOINT/$SHARE 2> /dev/null)" == "" ] ; then
echo "$MOUNTPOINT/$SHARE is empty."
else
su root -c busybox umount -l $MOUNTPOINT/$SHARE
fi
fi
# Show some results
RESULT=`mount | grep $MOUNTPOINT/$SHARE`
if [ "$RESULT" = "" ] ; then
echo "SUCCESS! $MOUNTPOINT/$SHARE has been unmounted."
else
echo "FAILED! $MOUNTPOINT/$SHARE could not be unmounted."
fi
echo
echo All done. You may close this script window now.
Hope this helps some of you. It sure stumped me how incredibly convoluted this simple and much needed procedure has become on Android 4.2.2... just because of that multi-account stuff and new restrictions on adb.
Credits:
Script bits and nls_utf8.ko by H3g3m0n
More script bits by dafunk60 and jmtw000
Punchmod by Jann Horn
Punchmod info by idcrisis
Thanks man, looks awesome, I am going to try it on my 6800.
Do you know how to mount ext4 or ntfs sdcard on CM10.1 based roms?
Removed the original post, still trying to make it work!
I checked vermagic in some existing ko files and found that it is exactly the same as yours.
Sent from my GT-p6800 using Tapatalk HD
m0bster said:
Removed the original post, still trying to make it work!
I checked vermagic in some existing ko files and found that it is exactly the same as yours.
Sent from my GT-p6800 using Tapatalk HD
Click to expand...
Click to collapse
You can try loading the UTF8 module without vermagic string as well, it should work on PAC. Or, make sure you have a blank space at the end of the vermagic string, it is required. Maybe read the short tutorial here: http://forum.xda-developers.com/showthread.php?p=41920265#post41920265
dfkt_ said:
You can try loading the UTF8 module without vermagic string as well, it should work on PAC. Or, make sure you have a blank space at the end of the vermagic string, it is required. Maybe read the short tutorial here: http://forum.xda-developers.com/showthread.php?p=41920265#post41920265
Click to expand...
Click to collapse
I finally managed to mount cifs shares, after loading original cifs and punmode load of nls_utf8.ko.
But I mounted it with cifsmanager. The script always shows "failure to mount" !
Project thread created..
http://forum.xda-developers.com/showthread.php?t=2627255
install-or-mount-v0.8-gui.zip
Use this thread for help
Device List
Change Log
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
ONDR4SH3K said:
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
Click to expand...
Click to collapse
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
userdelroot said:
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
Click to expand...
Click to collapse
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
ONDR4SH3K said:
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
Click to expand...
Click to collapse
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
Click to expand...
Click to collapse
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
ONDR4SH3K said:
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
Click to expand...
Click to collapse
Yea, it has to do with the line above I believe.
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
Click to expand...
Click to collapse
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
ONDR4SH3K said:
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
Click to expand...
Click to collapse
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
userdelroot said:
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
Click to expand...
Click to collapse
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
is it normall ubuntu for desktop or Ubuntu phone version?
desktop
JFizDaWiz said:
desktop
Click to expand...
Click to collapse
I'm confused
Does touch work? Or do we need OTG cables
milestoneman said:
I'm confused
Does touch work? Or do we need OTG cables
Click to expand...
Click to collapse
You need root, and an android device.
No OTG cables..
It build's a chroot image on the device, with android running in the background.
You can run X windows (only LXDE currently because it is lightwieght) on the device and then vnc into it from anywhere, even a desktop...
There are other tools out there for this however, they require you to download the images. Which are usually between 1gig - 4gigs.
Instead of downloading the images, this creates the image and only downloads approximately 200megs for the packages.
Thanks for the explanation, sounds great
Sent from my Nexus 7 using Tapatalk
ONDR4SH3K said:
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
Click to expand...
Click to collapse
Yea, crap, that was my bad, I should check where the system busybox is installed. It should default to /system/xbin
But some roms I guess put it in /system/sbin ? Possibly a typo on the rom developers part? LOL
Anyways, I will add code to correct this.
EDIT: How did you fix image 2?, as it should stop at the error in image type every time.
At any rate, image 2 error is because it can't find sh. in the install-or-mount/bin directory type this..
ls -l bin/
Make sure sh is symlinked to /system/bin/sh or /system/xbin/busybox if not that is causing the error in picture 2
it should look like this...
ls -l bin/
sh sh -> /system/xbin/busybox
If you don't see that do the following:
cd /data/local/install-or-mount
busybox touch bin-configs/sh
rm -rf .bin-configs-done
if you have something like that it should be ok, however to be safe since you moved you your busybox
from inside install-or-mount
rm -rf .bin-configs-done
Yes there is a DOT in front of bin-configs-done
I receive a permission denied error with debootstrap as well
Edit: crap I didn't see all the replies up there
Sent from my GT-N7105 using Tapatalk
Will it works on my armv7 single core tablet?
I fix it other way:
mount -o remount,rw /system
cp busybox /sbin /system/xbin
mount -o remount,ro /system
I hope that commands are fine.
I has no solution for fetch Release error, yet. I tried rewrite URL, but unsussesful.
Its in scripts folder line mirror_styles Release
Sent from my Xperia P using xda app-developers app
---------- Post added at 01:06 AM ---------- Previous post was at 01:00 AM ----------
Already testing on armv7 device dual core. OP must fix a few errors but you can try it.
Sent from my Xperia P using xda app-developers app