Database Info

[Q] Cisco AnyConnect for Rooted Devices

Has anyone got the Cisco Any Connect for Rooted Devices App to work on the TF??? I keep getting the "This device does not meet minimum requirements to run this software (TunTap driver could not be located)" error. Anyone find a workaround?

I'd root my TF in a sec if it will work. I've been trying to get this to work on my D2G but it also doesn't have a TunTap driver. I found tun.ko in one of the forums but have to had the chance to see how one might install it. I know some custom ROMs have it included.

works fine rooted prime + clemsyn 16

It seems that it is not able to load the tun.ko if it is present as a module. I had to use insmod /system/lib/modules/tun.ko to make it work. I have a stock kernel with just added tun.ko module.

Woah, didn't know this came out...thanks. Will give it a shot.
Edit: Appears to work fine, but I need get get my ASA license.

Awesome! Finally!

The app installs fine but when you try to connect is when you get that error. @ljs_cz, does the stock 3.1 come with the tun.ko module? If not where can I find one? I found a post with a module but its for 3.0.

Totally wasn't aware this existed. Works flawlessly on my TF running prime and clemsyn. This combined with RemoteRDP means I don't need to carry round my laptop when I'm on call!
Thank you OP, life-changer.

For those who are on stock 3.1 root, copy tun.ko to /system/lib/modules and
install it from a terminal, command "insmod tun.ko".
Check with command lsmod, you should see tun.ko loaded.
Install cisco anyconnect for rooted device and you are set.
Note, you will need to load tun.ko again after a reboot.
tun.ko, http://db.tt/ad4m1qB
Sent from my Transformer TF101 using Tapatalk

Thanks ill give that a try!!!

Ok its works great but when i restart the device the module isn't installed anymore and i have to insmod again. Any way to keep is installed after device boots???

help
gpmg762 said:
For those who are on stock 3.1 root, copy tun.ko to /system/lib/modules and
install it from a terminal, command "insmod tun.ko".
Check with command lsmod, you should see tun.ko loaded.
Install cisco anyconnect for rooted device and you are set.
Note, you will need to load tun.ko again after a reboot.
tun.ko,
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
i tried copying the tun.ko to /system/lib/modules but i got Permission Denied.
Is there another way to make this work?
I am rooted with build model 8.4.4.11

You need to mount the /system as RW before you can copy it. I am not sure of the ADB command, but you can do it through total commander (file manager) which is how I did it.

is it possible that you could give me a step by step guide as to how to accomplish this? i am trying but seem to be failing.

Bump, I could also use some help with ssretz's problem.

hmm..on ICS, tried your solution anyway. copied the file over to the location you specified, but when i run the command in the terminal it says no such file or directory.
Edit...i ran su -c insmod /system/xxx/xxx/tun.ko
i ran su earlier, but not on the same line.
that seems to register it. will test later.

still failing to copy files
Hi,
im running the TF PRIME 2 with ICS 4
im trying all of the suggested aboe and still failing to copy a file to the system/library/modules folder
any help?
i think it's a permission issue, my device IS rooted and i CAN copy files to the other SD folders

zipper9 said:
Hi,
im running the TF PRIME 2 with ICS 4
im trying all of the suggested aboe and still failing to copy a file to the system/library/modules folder
any help?
i think it's a permission issue, my device IS rooted and i CAN copy files to the other SD folders
Click to expand...
Click to collapse
I've done it via command line (you must mount the system directory in RW mode) using multiple iteration of the proper switches until it finally worked, but if you're struggling, just spend a couple bucks to buy Root Explorer. The aggravation you'll save will be well worth it.
Root Explorer has a button that will eliminate the command line instructions necessary to mount the system directory in RW mode and return it to R only, along with allowing you a simple copy/paste interface to move the files.

connects but does not route over tunnel with CM9/Megatron 1.0.1
Current system with issue: Megatron 1.0.1 with stock kernel.
Details:
I am able to connect using Rooted anyconnect, and I see my route table getting updated but when I try to access a resource on the vpn network it can not reach. I am not able to ping, ssh, rdc to any resource thru the tunnel. Local lan resources such as my own computer work fine or internet resources
I see the following interfaces get created after I connect:
-csctun0
-droptun0
My route table displays updated routes after vpn connects showing to use the iface of the cscotun0 for the resources that need to be routed thru. (192.*, 10.*, etc)
Funny thing is that I am able to use the stock 4.0 ICS and/or older honeycomb releases and it works fine. It's just with Megatron 1.0.1 or any CM9 rom. I tried using update-cm-9-20120329-NIGHTLY-tf101-signed.zip, still a nogo. Leads me to believe could be related to the CM9 trunk.
The logs between stock and CM9 flavored roms look the same on anyconnect. Nothing glaring.
lsmod doesn't show the tun module in as I believe now tun is compiled directly in the kernel (can someone confirm this?) (Running lsmod with stock doesn't show tun, nor in CM9/Megatron).
I love me some cyanogen and really like ricardopvz work especially the quick apps, but I need my vpn working for production support as its nice to work off the tablet when I am not near a computer.
Any help or direction will be greatly appreciated. Thanks in advance.

Confirmed that my problem only exists with CM9/Megatron roms
AOKP and stock based roms work fine. Any one else have this issue?
Sent from my Incredible 2 using XDA

[Q] Sensation CIFSManager with TempRoot

Ok, so the latest temp-root has gone well, and things still work okay, which is a great improvement, and much kudos to the devs for this.
However, CIFs Manager seems to not work, and I like to watch stuff over my network - and I'm pretty sure it's something very simple to do with SymLinks and stuff, as to how it works.
"Mounting the share has failed with an error
mount: mounting //10.1.100.10/Films on /mnt/cifs/Films failed: No such device"
Same settings work fine on my Desire, so I know the network's good, must be something to do with where it's looking, or trying to work, and the symlinks etc. in the temp-root.
However, I haven't a clue where to start - maybe someone can help out?

Maybe you start with reading the CifsManager FAQs?
regards
Most Frequently Asked Questions:
Q: When trying to mount a share I only get an error message saying something like...
"Error running exec().Command: [su]"
A: Most probably your device is not properly rooted or the su command is missing.
"No such device".
A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support.
"mounting <yourshare> on <yourmountpoint> failed: No such file or directory"
A: Your "Mount Point" simply does not exist and CifsManager is not able to automatically create it for you. As automatic Mount Point creation is not done with su rights, CifsManager can only create Mount Points in directories with permissions 777 or on your SD-Card.
Q: I have installed CifsManager but launching the app fails with something like "Application not installed on your phone"
A: This is not a problem caused by CifsManager but a bug in your ROMs launcher. Look for an updated version of your launcher.
Q: I mounted my favorite share successfully but files with special characters are not displayed correctly.
A: Try to use a kernel with explicit UTF-8 support or try to find/load the kernel module nls_utf8.ko.
Click to expand...
Click to collapse

f3d0r said:
Maybe you start with reading the CifsManager FAQs?
regards
Click to expand...
Click to collapse
fed0r,
Great information there - thank you so much. I'll double-check the permissions, but I was sure I'd already altered the mount point to 777. If that doesn't work, I'll try using a mount point on SD too.
I never even thought that the issue could be something so simple - thanks agaiN!

I thought he was indicating:
A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support.

Yes, on reading it the second time over, that seems to be what is indicated. I actually had an error combining #2 and #3.
Ah well, back to waiting for S-OFF so I can flash a ROM with the right kernel, because I haven't got a clue when it comes to Kernel type things!!
So, Stock Sensation ROMs do NOT have CIFS support. Tested.

mini how-to to _fake_ front camera for Google+ Hangouts

all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest

thanks to Kali- for the tips

Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!

Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?

jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide

Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work

This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)

Nice work... I'll try this one...

hello,
how to fix permission?
with a terminal

I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.

yep, but the problem I haven t a recovery mode. I want to say no menu.

I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?

just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.

Perfect!!! Thanks, works like a charm on my Nexus One

great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).

I tried the same to see if it would work for Talk on my Defy, but no success

[Q] CIFS Support

I'm using danalo1979's all in one EP4D posted here: http://forum.xda-developers.com/showthread.php?t=1365376
Currently using the debloated version, but have also used bloated. Either way, it uses the 4.0.0 version of IMoseyON's kernel.
Is it possible to add a CIFS module or something so that I can use CIFSManager and mount a share from my home server? I realize it'd only really work when at home on the local network, but it would still be quite useful.
Thanks.

Yes. If you can get VPN working, which currently is nearly completey worthless on the Charge (it won't pass VPN traffic even on EP4D) then CIFS would be completely sick as hell no matter where you werre.
Anyways, here is how I do it it. There are other ways to do this. This particular way is cool because it allows a simple way to restore CIFS's settings when you change ROMs or wipe, etc.
This is assuming you are using IMO 4.0 kernel and that you have root.
Have fun! Let me know if you have success or need help.
1. Go to Terminal Emulator and type "su", then "cifs enable"
2. Install Busybox 1.18.2
3. Copy cifs.ko and slow-work.ko modules into a folder called "cifs" on the SD card (these can be put anywhere, I just prefer the SD card because its fast and easy)
4. Install CIFS Manager
5. In CIFS Manager settings, check "Loads cifs module" and "Load via Insmod" checkboxes
6. In CIFS Manager settings, type "/sdcard/cifs/slow-work.ko:/sdcard/cifs/cifs.ko" into the the "Path to cifs.ko[:<modpath>]*" field.
7. In CIFS Manager, create a new share and enter the fields- example with computer IP address of 192.168.1.100 with network share called "share" and computer username and password "user" and "password" respectively.:
Share Path:
192.168.1.100/share
Mount Point:
/mnt/sdcard/convert
Username:
user
Password:
password
8. Save Share and restart phone
9. In CIFS Manager, click on a share to mount it
10. Profit!
Note that there is a module in /system/modules called bcm4329.ko that Imoseyon added to the kernel. I don't actually recall where I got my cifs.ko and slow-work.ko modules, but they were advertised for Froyo, possibly for the Galaxy S phone. I would be happy to provide the files if anyone is interested.
Note that the slow-work.ko module likely must be typed into the field first in Step 6.

Major cool. Thanks.
I'm searching for the cifs.ko and slow-work.ko modules now. When I find versions that work I'll go ahead and post them here. However, since you already have working versions it'd be great if you went ahead and posted them in case I can't find ones that work.

Actually, I just turned used the "CIFS enable" command as SU in terminal emulator and I'm now able to use CIFS Manager to mount stuff. I'm now trying to get Mount Manager to work as it appears to be able to automatically mount and unmount when you connect to a wireless network.
As you say, a working VPN solution would tie all this up in a nice bow....
Thanks again.

Interesting, I'm curious how you got it to mount without the modules. I recall getting "No Such Device" when mounting indicating the the kernel doesn't support it unless I point to the slow-work.ko and cifs.ko modules.
Can you describe what you did you get it working without using the modules?
Thanks
The ones I use:
http://www.megaupload.com/?d=IFOUQS9T
The GB ones that I haven't really used:
http://www.megaupload.com/?d=456718D0
By the way, PPTP works fine on ICS. I tested it on the Galaxy Nexus. I don't know about CIFS support on the Galaxy Nexus though.

Absolutely nothing.
I'm using danalo1979's easy all in one odin. I simply opened a terminal emulator, typed SU and then typed "CIFS enable". Upon a reboot I was able to access the share using CIFSManger. Still haven't messed with Mount Manager to automate the remounts.

Need help to modify a kernel

Hi everyone,
I have a 10.1'' chinese tablet with a rk3066 chip, suddenly the firmware got damagend, there is no way to find the original, i've tried with over 100 different firmwares from here or rockchipfirmware, nothing worked, but there is 1 version that barely works (PlayerMomo12 release 3) but the screen is inverted in both axis (X and Y), i've tried different methods to fix it, with apks, with usb debugging, and nothing worked, the apps just doesn't works, even one of them dissapeared and i was unable to install it again, using my laptop doesnt works because the directory that should mount doesn't exist, i don't know why but i've tried all the methods, even mounting with a terminal inside the tablet (you can imagine how hard was writting with the screen like a mirror), then i thought the only solution was using the kitchen to modify the file script.bin, but again, a lot of problems, i couldn't open the image, found this thread:
http://forum.xda-developers.com/showthread.php?t=633246&page=555
-------------------------------------
Originally Posted by biglcny
just running sysrw and sysro would return this:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rather than no output as usual. I believe there may be another version of mount that takes different parameters. When a rom is flashed and you connect to it with adb shell there is a version of mount in /system/bin that is different and accepts options in a different format.
simply typing running mount at the command line or in a shell script uses that one instead of the busybox one.
dr.notor replied:
Well, the above is an example of totally screwed up mount binary, dunno which phone and ROM you are using but the guy who produced the above would deserve a bit hit with a cluebat into their head.
If you have similar broken crap, simply edit the scripts to call busybox mount and not mount.
-------------------------------------
well, this is the point (after a lot of days working on this) when i give up, this tablet was bought in China and the company (scope) doesn't sell it anymore, and they don't reply the emails, even the webpage is half empty, this is the point when i ask, if someone can help me sending a working kernel based on this rom (PlayerMomo12 release 3) or the firmware with the script.bin modified to invert both axis, if no one can, then it's the moment to smash the tablet with a giant hammer and send it back to China
i could bought 2 galaxy tab 4 if i wasn't wasted so much time on this
here is the firmware if someone wanna to try
http://www.rockchipfirmware.com/content/ployer-momo-12-tnt-release-3

http://forum.xda-developers.com/showthread.php?t=863209
Thread closed