I have wasted more than 3 days trying to figure out how to configure openvpn
on S2.
I tried the following roms:
Villainrom 1.4
Cognition S2 v1.07
Skyrom 1.0
Lite'ning Rom v1.5
and none of them seems to work.
I tried everything mentioned in :
http://forum.xda-developers.com/showthread.php?t=1115984&highlight=openvpn
http://forum.xda-developers.com/showthread.php?t=1074492&highlight=openvpn
but openvpn does not work.
I also own a HTC desire and configuration files work without a problem.
I tried manually installing openvpn as described in the posts but it does not work.
The problems are:
If I install openvpn manually as described in the threads above it does not connect to the openvpn server.
I installed openvpn from the market by selecting the folder for the binary
/system/xbin
and tried all the possibilities for path for ifconfig/route.
- /system/bin
- /system/xbin
- /system/xbin/bb
The default folder for ifconfig/route should be /system/bin (result from which ifconfig) and only that selection does not give the horrible
"FATAL: Linux ifconfig failed: could not execute external program".
but openvpn still does not work.
Any ideas ?
Hello,
I have the same problem, with same error
but I have successfully get connected to my vpn (vpntunnel.se) but its useless since the route doesnt use the vpn connection.
If anyone could help...
i have same problem too. some help would be good
Could this help?
I'd love to get this working too but I have not made any attempts yet so I'm monitoring this thread.
Searching for that exact error message on google led me to this thread which you may already have found.
In particular, even though it's about the galaxy i5800, the following comment may shed some light:
you may not use the pre-installed busybox from samsung (which is found in /sbin). It is a reduced version of busybox that does not include suitable ifconfig- and route-commands for openvpn. thus you have to install a full version of busybox... normally this is done, when you root your phone according to descriptions found in this forum.
you can alternatively install titanium backup (which installs its own busybox) and copy the "full" busybox from titanum backup to /system/xbin.
Click to expand...
Click to collapse
Try to do it but impossible for me. Im with lite ing rom. Check my configuration tomorow
Sent from my GT-I9100 using XDA App
Alright, so after going nutts (several times) I solved this issue (several times) only to always find I dont really know what the error is. But then again, I know more about Geological disasters than I know about Android ...
Anyways, heres my solution which appears to work. However, it goes away once you reboot (easily fixed) and disappears completely after you update firmware - but I made shortcuts.
The thing is, that the original busybox is not installed where openvpn looks for it. Regardless of this, openvpn has no idea how to use ifconfig / route commands in /system/bin directory.
So this is what I do:
1) Install busybox (from the market, get ver 1.19) to /system/xbin
2) Install openvpn to /system/xbin and point ifconfig/route to /system/xbin/bb (during installation).
3) Link the new busybox to the /bb directory MANUALLY with these commands (customized to steps 1/2 - you can change them to your liking but dont forget to update step 3 as well):
ln -s /system/xbin/busybox /system/xbin/bb/ifconfig
ln -s /system/xbin/busybox /system/xbin/bb/route
Click to expand...
Click to collapse
What it does is place a busybox link to ifconfig and route in /bb directory.
Funny thing - Whenever I tried linking ifconfig/route to other places (like /system/xbin) it just didn't work. It made the tunnel, but tun0 int was always down (thats why it says "connect to as xx.xx.xx.xx" missing the tunnel internal IP - as in, no routing).
Challanges - when you soft reset, something dies. Not sure if its the busybox or the links. However, simply "reinstalling" busybox to /system/xbin solves it (its not really reinstalling, its just going into the busybox installer. Its only recreating links).
When you install an update/new cfw, everything dies. Reinstall busybox and re-enter the link commands.
Hope this helps, hope some android programmer tells me why it works this way. gluck.
Related
I've compiled 2.1 from source and I ran in to a problem. The device will boot and the touchscreen,keyboard, apps, and the phone all work but i'm having a problem trying to install apps from the marketplace. when i download an app it will download ok but always says installation unsuccessful and says insufficient storage. I checked the phone storage and it's over 100mb so i'm clueless as to why i'm getting this error.
I'm also having problems getting the sound working. I can select ringtones but nothing ever plays. I've copied the proprietary files from a ROM i was using on the device prior to flashing this and added them into this ROM. any help is greatly appreciated.
1) Try this from a command prompt (terminal app or adb shell):
chown system.system /data/app
chmod 0771 /data/app
If this works, you should add this to your update-script before flashing again:
set_perm 1000 1000 0771 DATA:app
2) Not sure about the sound issues, although I have an AOSP 2.2 ROM that acts the exact same way.
you actually inspired me to try to make my own ROM. I used your android builder and dsixda's kitchen. let me know if you figure something out with the sounds. It took me long enough to figure out how to get it to recognize the SD card.
That worked. I'm also havings issues with the camera and softkey lights. i copied the lights file into the proper folder but they still don't work. camera doesn't do anything either.
setcpu also for some reason can't get root either, it says root access not detected but i have su in /system/bin. too many problems!
update. apparently my permissions are somehow screwed up. i can use ADB and have root access but from the device itself using a terminal emulator i've figured out i don't have full root. any suggestions?
fixed the su issues. i had to adb remount and adb shell and chmod 06755 /system/bin/su if anyone was wondering
I'm still having issues with sound, camera, etc. i have moved all the proprietary files from a stock HTC 2.1 ROM over and i'm still having problems. I'm now using the new CFS kernel from conap and decad3nce and got overclocking to work. The main problems are sound and the softkey lights, once i get those working i can use this ROM everyday and work on the wifi, bluetooth and camera. If anyone has any tips or knows any other libs that might work it would be great.
Hi! Sorry if this question was already asked, but I couldn't find something related..
I have SGS2 XXKG3, so I've downloaded Chainfires's rooted kernel XXKG3 and successfully flashed it. Then I tried to install SUFBS (root file manager and terminal) and it told me that I don't have busybox when I tried to mount /system as r/w. Also it offered to install free busybox from Market. I agreed.
Everything seemed to be OK until I found that droidwall cannot show me the log - it tells "dmesg: applet not found". Little research discovered that I have symlink /sbin/dmesg which refers to busybox. But my version of busybox doesn't support dmesg. Also I'd found normal dmesg (ELF-executable) under (probably, I don't remember) /system/bin. So I deleted the symlink (/sbin/dmesg) and everything worked OK again. But.. till reboot. After reboot the /sbin/dmesg was there again.
Little more research and I found that now I have two versions of busybox on my SGS2: one from Chainfire's kernel (dated 2009) and one that I've installed myself (dated 2011, sep). The latter (2011) has about 1.5 times more functions that Chainfire's. But 2009 has dmesg function whereas 2011 hasn't.
So here is the question: why /sbin/dmesg is automatically restored after boot? And what can I do to prevent it from restoring?
Also, do I need to do something to remove one copy of busybox or two of them will live OK with each other?
Guys, please help... I can't now write to developers' forums since I don't have enough posts, so my only hope is to write here
Hi im trying to change my wifi mac address.
i tryed this one
http://forum.xda-developers.com/showthread.php?t=1385577 but it's not working and many other way and almost any app on the market .
so please if anyone change his mac on Mini pro Please help.
Got root and busybox?
Sent from my WT19i using xda premium
I did and it's not working not on Xperia Mini Pro.
REQUIREMENTS
1) ROOTED PHONE
2) BUSYBOX INSTALLED
3) Terminal App
OPEN UP TERMINAL AND WRITE
:su
:busybox iplink show eth0
(THIS WILL SHOW YOUR CURRENT MAC ADDRESS)
NOW TYPE IN
:busybox ifconfig eth0 hw ether 00:11:22:33:44:55
(INSTEAD OF 00:11:22:33:44:55, YOU CAN WRITE YOUR WANTED ADDRESS)
Click to expand...
Click to collapse
And what happens then?
Explain, what does it show, what error or what message comes up.
Code:
Ifconfig: SIOCSIFHWADDR: Operation not supported
Thank you for your relpay.
@ murders10: are you sure the root worked? what firmware are you running? are you using the right interface, is it eth0 that you wanna change?
Yes im sure root it's working fine Stock Rom .62.interface Wlan0 There is no eth0 on Xperia.
I did the same thing but it replied me:applet not found...
I need some help
I hope someone can help as.
Sent from my SK17i using xda premium
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
it won't work with me what ever i did remove reinstall
But after all i fix my god dam router mac address problem. so i don't need to change any mac . thank you for the help.
Need to change MAC Address to try if Heywire works on a custom rom
urra901109 said:
Its wlan0 not eth0..
edit: my phone gets the same error.. solved by re-installing busybox
1.play store>busybox (by stericsson)
2. run busybox app from drawer.. and choose install.
my first time installing the busybox from busybox installer app gives me some error that i dont have time to read through . something about old copies. i close it and start over. everything is just fine.
Sent from my Xperia Mini Pro using xda premium
Click to expand...
Click to collapse
I'm trying this, but get a message error in terminal emulator, when i type :su, theres a message that says :su: not found, or :busybox ..., the same :busybox: not found error displays.
I'm runing Real ICS lite r2, on my Sk17a, with locked bootloader, stock kernel, rooted, with busybox 1.20 installed,
Im trying this because i use heywire a lot, and this rom is the best ive tried, and its awesome, lighting fast, but heywire says this phone has a previous heywire number, and as i investigated, it has something to do with the MAC address, give me some light here please
ipconfig: applet not found - MAC spoofing
Someguyfromhell said:
And what happens then?
Explain, what does it show, what error or what message comes up.
Click to expand...
Click to collapse
Hello, I've been trying to follow this guide at:
http://forum.xda-developers.com/showthread.php?t=1385577
My phone has CM 7.2,busybox installed too.
Entering
Code:
busybox ifconfig
in terminal (not in su) gives me the local loopback address, and when I turn on my wifi, it shows my wifi card details too. (It's named tiwlan0 though)
Anyhow, since ifconfig needs to be run as root, I get ifconfig: applet not found after I enter following commands:
Code:
$su
#busybox ifconfig (and anything starting with this)
So it looks like ifconfig runs fine without su but is not detected at all after I make the switch to su. And since the line of code that changes the MAC cannot be run without su(then I get - SIOCSIFHWADDR: operation not permitted), I am stuck!
I tried other methods such as and similar to the one on
http://forum.xda-developers.com/showthread.php?t=1343695
where, after editing some configuration file, one could change his MAC address. Is there any such known file/method for the LWW?
Thanks!
Simple Tutorial to spoof MAC address
So I finally figured this out and it actually works for the purpose u needed, I will write down step by step guide, and write me if you need some help
1. You need your XMP to be rooted, with SU intalled, busybox installed and with terminal emulator app
2. Open terminal emulator app, and type: su
3.Allow terminal app to have super user access
4.Now type: busybox ifconfig (with your WiFi on)
5.Locate the text on the left side "wlan0" and in that paragraph locate HWaddr, write down this address just in case.
6.Now turn your WiFi off
7.In terminal write down this: busybox ifconfig wlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
8. Turn on your WiFi, And your MAC address should be the one you created (you can check that by typing in terminal: busybox ifconfig)
And ther you go, you spoofed your WLAN MAC address, tested by me in a simple tutorial, hope it helps
---------- Post added at 01:58 AM ---------- Previous post was at 01:52 AM ----------
In your case step 7 should be like this:
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
7.In terminal write down this: busybox ifconfig tiwlan0 hw ether 0A:1B:2C:3D:4E:5F (remember 0A:1B:2C:3D:4E:5F is only an example, you should follow the pattern: number, letter, number letter an so and on, for this process to work).
I'm running Real ICS r5.1 by the way, and now heywire works just perfect. In step 7 tiwlan0 should be renamed as the name the card shows when you first run only ifconfig, take that as an advice.
Click to expand...
Click to collapse
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
blackstallion1234 said:
No, it doesn't work. Like I mentioned previously, everything is seemingly installed(SU,busybox,terminal- iam on CM7.2 anyway) but in su mode,
Code:
busybox ifconfig
says ifconfig: applet not found. Am I the only one with this problem? Also, I'm not sure I should replace my terminal with the one from the market.(read somewhere that it does some replacement stuff; don't want to re-flash again soon)
Click to expand...
Click to collapse
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Problem with busybox probably...
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
pikpok said:
Code:
su
ip link set wlan0 address aa:bb:cc:dd:ee:ff
Of course change example address to yours. It works until reboot.
Click to expand...
Click to collapse
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Xtrifer said:
Why dont you try this, reinstall busybox via google play, with the app by Stephen Stericson, then you open the app, and grant BusyBox super user access, later you use terminal app and try my process, if not, then try the process posted by pikpok, see if it works and tell us
Click to expand...
Click to collapse
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
nice
blackstallion1234 said:
Uh sorry my internet had been down almost a week! I installed MIUI v2.7.27 meanwhile and this time I could change my MAC address!
Couldn't try that. But thanks, will keep this in mind in the future.:good:
Yeah, busybox probably was the problem with CyanogenMod 7 (which has a different version of busybox than the one that came with MIUI 2.7.27). Maybe it hadn't been installed right somehow with CM7..
Anyway, it does work!:victory:Thank you!
Click to expand...
Click to collapse
Good, I was sure it was busybox, don't forget to hit the thanks button, happy modding lol
Hi,
I tried to upgrade the busybox with different manner (busybox, busybox installer, manual installation from xda), but no one works properly.
Each time i broke the original Archos busibox, so i lose the adb shell.
Can someone explain to me the good way to upgrade the busybox?
Thanks.
SirOch
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
SirOch said:
Hi,
Nobody to explain a clean upgrade of the busybox?
cheers
Click to expand...
Click to collapse
Google? also XDA has a great search feature have you tried that? :silly: Any particular reason why you want/need to upgrade busybox?
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
SirOch said:
Hi,
As i said, i tried the different busybox installers and the installation was ok, but i each time, i lost the shell from adb.
That's just my problem.
So i just want to understand why the upgrade of the busybox broke the original archos busybox?
Moreover some application need to have other busybox installed.
Regards.
David
Click to expand...
Click to collapse
Ahhh right, the quest for knowledge Your problem is as much to do with adb ( /sbin/adbd to be precise ) as it is to do with busybox, firstly you've probably wiped out the symlinks in /bin, especially /bin/sh which is the location that adbd on archos looks to run the when you do adb shell from your desktop. This is not the default location which just about every other android OEM adheares ,that is /system/bin/sh.
If you are going to upgrade the archos busybox be aware that a large number of symlinks back to /bin/busybox exist not only in /bin but also in /usr/bin /usr/sbin
Archos for reasons I still haven't fathomed, really went to town on restructuring and customized Android on the platform level.
A little tip if you've got more question, to save you bumping threads , which really does upset some folks round here... you'll probably get more more if you add more details, such as error messages etc. Saying " i lost the shell from adb." doesn't really help anyone who might be able to offer assistance. There about 10 different ways adb can fail to connect, Did the device disappear from the list or report as offline. or even come up with the message "- exec '/bin/sh' failed: No such file or directory (2) -".??
Hopefully that's helped.
Hi SirOrch,
i don't know why you loose your adb shell, but concerning busybox... the things on Archos tablets are like this:
Basically on a non rooted device we got a squashfs image mounted read only.
This image contains the stock busybox compiled by Archos (sharing system's uclibc) with limited functionality,
but containing enough tools to handle the daily job.
The path to this busybox is "hard-coded" as well. It's location is /bin which is the second entry in the path environment.
You might check that by typing printenv in your console.
The first entry should be /data/local/bin on your device.
So if you like to replace stock busybox with an advanced one, you should make sure that it will be installed to /data/local/bin.
Often there's no need to use all this apk Android Market stuff to get a proper busybox installation.
Sometimes it's little better to really understand what's happening under the hood.
Most busybox app's are statically linked, because with a static binary you don't have to take care of the device's libc or uclibc.
So you might easily extract on of the apk's or get one from xda-developers.
There are many floating around in the end.
If got one push it to /data/local/bin with adb.
You might need softlinks in this directory as well. This could be done by hand as well.
Anyway if you are a lazy person, who doesn't care about what's happening, go to the market install busybox.
Then check at /data/local/bin if it is there.
If it got installed elsewhere, some commands will still use stock busybox.
Extended commands might then use the installed one.
So check it out...
EDIT:
... aaaargh again simultaneous posting.
scholbert
Hi gentlemen,
Thanks for your help and sorry to forget to give you the error message i had:
the message was : - exec '/bin/sh' failed: No such file or directory (2) -
After investigation i found my mistake:
- In manual mode, i forget to change the ownership of busybox to root in /bin.
- when i tried to use any application from the market, the busybox was well updated in /system/xbin but the application also delete the busybox in /bin and don't change the symlinks in /bin. That's explain why adb shell won't work.
Regards.
SirOch
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Please help
MonaLisaOverdrive said:
I thought I'd post this...even though I'm a noob...so that others can benefit if possible. If you're using the JRummy BusyBox installer, please be careful with the Advanced Install option. Here's why:
After rooting my phone I installed JRummy's BusyBox installer. First, after checking busybox.net for the latest stable install version, I did a full install without the symlink apps option selected. Then I did another full install with the symlink apps option checked. Finally, after reading through the entire list of available commands and what they did, I decided to do an advanced install. I selected "Remove Symlinks" for each of the busybox commands I wanted NOT to have available in Terminal Emulator.
Soon after the advanced installation, I noticed that Terminal Emulator wasn't working. Then I noticed that my WiFi connection wasn't working...specifically the part in which the phone attempts to lease an address using DHCP. After emailing the developer with my issue, I tried to re-install BusyBox manually based on a link he included in the reply. I could push the file to the phone using 'adb push' but when I tried to open a shell to run the install commands, I would get the following error: exec '/system/bin/sh' failed: No such file or directory (2) . Long story short, I had to re-flash the phone using Odin to fix it.
In the AFWall+ logs, around the time I ran the Advanced Install, there were a bunch of entries like this: ld_library_path=/vendor/lib:/system/lib busybox rm /system/xbin/strings exit. There may have been a -s after the 'rm' command and before the directory but I'm not completely sure. After I flashed the phone with Odin, I opened Root Explorer and took a look at the files under /system/bin/. I noticed that the commands that can be run without installing busybox...like ls, or ifconfig...were linked to 'toolbox'. /system/bin/sh was linked to mksh.
After more research and reading, I'm about 90% sure what happened. Here's an excerpt from the email I sent to the developer:
<snip>
Basically, the "Remove Symlinks" option in your app does either one of two things:
It removes the directories entirely
It removes the symlinks to busybox, but doesn't restore the original symlinks that were present before busybox was installed.
<snip>
So if you're using this particular installer, please be careful with the Advanced Option.
Click to expand...
Click to collapse
Hello I installed BusyBox and I had same issue with WIFI also others for example after reboot of my tablet wholle setting is set to orignaly(language and everithing).How can put back everithing?Does exist some apps etc???Thank you.
OMG... i installed busybox with this app into /system/xbin on my dopo d7015 with advanced install... and then the problems started... 0 total internal size, wifi not acquiring ip with dhcp ... no factory restore could fix it. then i eventually learned that /system/bin/sh didn't exist when trying to adb shell. i've downloaded an sh binary and copied it, now i have valid internal total size, and android terminal works... but wifi won't even turn on now! like an idiot i didn't backup before i started playing with the tablet... i have no clue as to how to fix it! please someone help me!
With one version of this app, it said Busy box 1.20.x is not compatible for my phone. But busy box installer by Stericson does the job perfectly.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands