I am having problems with openvpn and I would really appreciate any help that I can get. I was not able to make openvpn work on Eagle Blood rom. Here are the steps I used. I installed binary file at the system/xbin using the openvpn installer from the market. I then created a folder at the root of sdcard and named it openvpn. I placed in the folder the configuration files. I then downloaded and installed openvpn settings from the market and tried to connect to openvpn. It would connect to the server (a small key would appear on the top of the screen and says connected) but data would not be tunneled through the vpn. My real IP address would still show while connected to vpn.
BTW, I flashed cyanogenmod 7 nighties #53 and it worked. I use simple mobile and data does not work with cyanogen since the APN needs to manually configured and with all the APN issues going on with cyanogen at this time, I would prefer to use another rom that would support openvpn.
Thanks in advance and I apologize in advance if I posted this at a wrong place. I am new to XDA forums.
Hello there,
I have a nice little sbkv2 tf101, and I wish to install a clean Ubuntu on it in dualboot.
So I followed the http://forum.xda-developers.com/showthread.php?t=1852702 and I tried to do it, it seemed quite simple.
I used the Olife wheelie updater to send the ubuntu.img found in the last thread (and renamed into ubuntu.img) and some packages for android.
Everything was send successfully.
I did the setup thing and configure the wpa_supplicant.conf (and removed other config):
Code:
network = {
[INDENT]ssid="myconnectblabla"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
psk="mypasswordyouwontseehere"[/INDENT]
}
I didn't change much...
My router use the WPA-TKIP protection (I dont have more information about)
I then rebooted and I found the message:
wait for connection
60 sec ..blabla
and falling back to the commandline entries.
My question is : do we have to add some special driver update? I can't see why it is not working...
I also tried:
change in my router: password, WEP, WPA-TKIP+AEP, and some other configuration.
different configuration of wpa_supplicant.conf using howtos
change the kernel with Jhinta's one (I had some kernel panic...)
I assume I'm quite a newbie but I can't find anything extremely clear anywhere about it...
Somebody have any idea how to successfully connect it to my network?
We know that Android L Preview release have same issues : One of this is Wifi/USB Tethering not works.
I find on xda a temporary fix for this issue (thanks buraktamturk) http://forum.xda-developers.com/showpost.php?p=54067884&postcount=3041
I simply done a shell script that give you and install the default gateway ip for your active data connection.
So every time you active a new data connection and you must done a tethering Wifi/USB condivision,
remember to run before this script.
Whats you need for make it work.
FIRST INSTALLATION
Your device must be rooted and you must have busybox installated link: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Install Root Explorer from play store (is not free) https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
You need it for execute wifi-tethering-lpv-fix.sh (you can also use terminal emulator even if you need more steps)
Download and Unzip the script attached and save it on your Nexus5 folder (i.e. /system) and give permission rwx (read-write-execute) with root explorer apk. (or chmod 777 wifi-tethering-lpv-fix.sh with terminal emulator)
RUN WIFI/USB TETHERING SCRIPT
After that every time you start a new data connection done this steps:
1. Run wifi-tethering-lpv-fix.sh with Root exlorer apk
2. Enable and disable tethering ; After that re-enable it. (this step is important otherwise dhcp server is not started - internal bug from Android L preview)
Now your USB or WIFI tethering connection would be work.:good:
An interesting problem...
davidmore said:
We know that Android L Preview release have same issues : One of this is Wifi/USB Tethering not works.
I find on xda a temporary fix for this issue (thanks buraktamturk) http://forum.xda-developers.com/showpost.php?p=54067884&postcount=3041
I simply done a shell script that give you and install the default gateway ip for your active data connection.
So every time you active a new data connection and you must done a tethering Wifi/USB condivision,
remember to run before this script.
Whats you need for make it work.
FIRST INSTALLATION
Your device must be rooted and you must have busybox installated link: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Install Root Explorer from play store (is not free) https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
You need it for execute wifi-tethering-lpv-fix.sh (you can also use terminal emulator even if you need more steps)
Download and Unzip the script attached and save it on your Nexus5 folder (i.e. /system) and give permission rwx (read-write-execute) with root explorer apk. (or chmod 777 wifi-tethering-lpv-fix.sh with terminal emulator)
RUN WIFI/USB TETHERING SCRIPT
After that every time you start a new data connection done this steps:
1. Run wifi-tethering-lpv-fix.sh with Root exlorer apk
2. Enable and disable tethering ; After that re-enable it. (this step is important otherwise dhcp server is not started - internal bug from Android L preview)
Now your USB or WIFI tethering connection would be work.:good:
Click to expand...
Click to collapse
Ok, so between your post and the other fix that you have posted, i have had SOME success, but is this significant?
I have a Nexus 5, that generally has a sim card i use primarily for data, which is on Aldimobile (MVNO using the Telstra 3g network), at the time i first tried this, i had an Amaysim (MVNO using Optus 3g network) inserted. So heres what happened -
I first followed your procedure (Amaysim card inserted, unsure how or if this is significant) , which allowed me to create a wifi hotspot connection between the laptop and the mobile. The effect was actually almost immediate when i ran your script. This did not allow any data throughput.
I then used the procedure you have provided in your link above, and bamf, i had a working wifi tether connection. Easy as pie.
I can report that it is repeatable, and you can enable then disable tether at will, until you reset the phone, and you have to go through the whole shebang again (i presume due to your mobile provider updating your ip address)
BUT - I then wanted to use my Aldi mobile in it, as the Amaysim is the one i generally use in my general purpose mobile, so i slapped the Aldi sim into the mobile... and.... nothing.
No amount of fiddling around with resetting the tether, changing settings, your script, the other script, would allow either a tether or data throughput.
Any ideas?
No need more this my script !! New Android pre-relase lollipox (LPX13D) have fixed it. Wi-fi and USB thethering works no more bug
Awesome
davidmore said:
No need more this my script !! New Android pre-relase lollipox (LPX13D) have fixed it. Wi-fi and USB thethering works no more bug
Click to expand...
Click to collapse
Cheers for that info, i hadnt found anything mentioning updates fixing this. Ill go download it.
Thanks for the quick reply, and good work.
This is a massive bump but it might help someone:
I had an issue on my Nexus 5X running 7.1.2 (beta), it had the same symptoms as OP; no default gateway, WiFi & USB tethering not working
Ran this script and now it works again, so the bug has either returned or wasn't fully fixed
Hi all,
I am trying to create an update.zip file to root a polaroid MID2X07PXA 7 inch tablet. I couldn't get root access via any of the one click methods. I previously had success with other android systems with the update.zip method (copy su to /system/bin and chmod 6755 it). I have a working example, except it mounts the wrong device. I simply wanted to change the script to mount the correct device. I have scoured the forum and the net, and keep getting the old:
"Footer is wrong"...
problem. I have successfully enabled adb, and can get into recovery mode. I have unzipped the working (well, it runs - just doesn't work) example, and rezipped, aligned and signed it and it doesn't work. I have tried various combinations as well. I have downloaded UpdatezipCreator (from xda-developers) which had the same effect "Footer is wrong". I have tried linux, windows XP (yes a very old system), windows 8 and windows 10, just in case the zip executable is different. What am I missing? I have downloaded SignAPK, and various other utils. I have tried the certificates that came with the signers, as well as one I generated with openssl.
Is there something I am missing? Is this tablet un-rootable? I really need to enable USB networking which I need root for - there is no tethering option in networks.
Quite frustrating. Any help is appreciated
Cheers,
J
Hi there,
I guess this thread will answers to all your querry:
[TUTORIAL] Create your own UPDATE.ZIP
[GUIDE][NOOB FRIENDLY]How To Make Aroma Installer Flashable Zip/update.zip
For more question you must register an account on XDA and ask directly in one of that threads or here:
[HELP THREAD] Ask ANY Question. Noob Friendly.
Good luck
So I got twrp 3.0.2_2016-04-17 p1 multirom working. I installed a few roms in primary and have moved to secondary but can only boot while in primary slot (kexec issue I assume) Really trying to get kali up and running and not so much kexec (will move back and forth for now) . found a lots of readme which looked good but diddn't quite work out. when kali would boot the nethunter terninal app would fail saying it couldn't find bootkali_login and I could never really uninstall changeroot. from twrp file manager I deleted /data/local/nhunter* and did complete reinstalls and still same results. I installed nh-op1-kali3.0 over cm13 and also found all in one 7.1 lineageos vers 14.0-20170101-unoffical and same results. I cannot find a cm11 or cm12 compatible with kali3.0 should I step down to kali2.0? any help or direction is greatly appreciated.
@seanwlk
Why dual boot? What do you need multirom for?
You can flash LineageOS 14.1 root it, and install busybox.
Then you need the nethunter apk and install chroot from there. (Chose either minimal or full doesn't matter)
The "issue" comes now basically I've tried multiple times to make the nethunter terminal work but it doesn't connect to Kali. So I managed to find a workaround which is basically using Kali over SSH and I suggest you JuiceSSH (but every SSH client will work) just connect to 127.0.0.1 (which is localhost, where Kali runs) but since the SSH service doesn't start on boot you will need to start it manually on each reboot through the nethunter app by creating a custom command that will be sent to Kali
Code:
service ssh start
Now you'll be able to connect and use Kali terminal.
It may not be perfect but I use it on daily bases.
I do this since COS 13 days.
Here I add some useful material.
Thanks for the responses. I found flashing the cm 13.1.2 original image when my phone would keep failing installs helped when I kept getting failed installs. got it and running on cm12 5.1.1 works great.... except for when it suddenly and randomly freezes the whole system with the screen on. I ran the Y-cable service and tried it out and it worked great. wifite as normal. I will give lineage14.1 a try. thanks for the heads up. as far as using multirom..... I found it copies the files from secondary to primary faster than a nandroid restore. I think its because the partitions are not zipped. 64gb is more than enough space that speed vs disk space wins. I have been using an lg g3 for years now and I really do like opo. got my tempered screen and tpu case yesterday so it's now traveling safely with me . My only concerns with lineage14.1 is that it might not support the wifi adapters in the kernel for external wifi adapters.
seanwlk said:
Why dual boot? What do you need multirom for?
You can flash LineageOS 14.1 root it, and install busybox.
Then you need the nethunter apk and install chroot from there. (Chose either minimal or full doesn't matter)
The "issue" comes now basically I've tried multiple times to make the nethunter terminal work but it doesn't connect to Kali. So I managed to find a workaround which is basically using Kali over SSH and I suggest you JuiceSSH (but every SSH client will work) just connect to 127.0.0.1 (which is localhost, where Kali runs) but since the SSH service doesn't start on boot you will need to start it manually on each reboot through the nethunter app by creating a custom command that will be sent to Kali
Code:
service ssh start
Now you'll be able to connect and use Kali terminal.
It may not be perfect but I use it on daily bases.
I do this since COS 13 days.
Click to expand...
Click to collapse
Nice!
I was having the same issue when I was running it on cm13. every time I tried to run android terminal in chroot kali it would fail cause it couldn't find bootkali. I thought it was just a chroot issue but if it works through ssh than that works for me! come to think of it. I never even tried vnc'ing cause I assumed it was not working. ssh much better than vnc for cpu overhead for sure.
rp201 said:
Nice!
I was having the same issue when I was running it on cm13. every time I tried to run android terminal in chroot kali it would fail cause it couldn't find bootkali. I thought it was just a chroot issue but if it works through ssh than that works for me! come to think of it. I never even tried vnc'ing cause I assumed it was not working. ssh much better than vnc for cpu overhead for sure.
Click to expand...
Click to collapse
I've tried VNC for the sake of curiosity. I installed xrdp but I can't login for some reason it gets stuck on the login form. But no big deal I don't need UI.
I hope I helped somebody, not sure if this method I use got ever published on the Internet ?
I installed latest nightly of lineage14.1 5/29/2017. Debug is enable and allowed over adb. (root priv for apps not built into lineage) then after inital boot twrp install of superSUv2.82 then your busybox and your nethunter. its not working for me. ssh service wont start. chroot is installed but not working. I'm obviously doing something wrong here. I can SU in terminal but cannot run "bootkali" or "bootkali_login" which is the error nethunter app is giving me.
rp201 said:
I installed latest nightly of lineage14.1 5/29/2017. Debug is enable and allowed over adb. (root priv for apps not built into lineage) then after inital boot twrp install of superSUv2.82 then your busybox and your nethunter. its not working for me. ssh service wont start. chroot is installed but not working. I'm obviously doing something wrong here. I can SU in terminal but cannot run "bootkali" or "bootkali_login" which is the error nethunter app is giving me.
Click to expand...
Click to collapse
Are you sure that the chroot is correctly installed?
Should be mounted here
Code:
/data/local/nhsystem/kali-armhf
Also when you boot the phone does the nethunter notification popup saying the boot went all OK?
How are you starting the SSH service?
Here check these screenshots: https://imgur.com/a/TYqoc
Also remember that Kali has an user and password so connect to SSH with the following credentials:
Code:
Host: 127.0.0.1
User: root
Pass: toor
seanwik,
yes to all of that I got everything the same. I was connecting as root to 127.0.0.1 but I was also thinking sshd.conf needed to be set to allow for root access possibly? but I never had to before so I have to guess sshd did not launch at start up. are you using a thrid party kernel?
rp201 said:
seanwik,
yes to all of that I got everything the same. I was connecting as root to 127.0.0.1 but I was also thinking sshd.conf needed to be set to allow for root access possibly? but I never had to before so I have to guess sshd did not launch at start up. are you using a thrid party kernel?
Click to expand...
Click to collapse
None of those commands start at startup, for the same reason nethunter terminal doesn't work, to have to run that custom command from within the app, only that way works. Also I don't use SuperSU but the root enabler for LineageOS so I used privacy guard as root manager. Don't think that's the issue, was just saying.
I'm currently running LineageOS kernel, but this method worked even with Boeffla
Look:
(sorry for my ****ty voice ? )
I fully clean reinstalled my ROM like 2 days ago and did this as usual and works.
thanks for the video and your time. did a new install. stilll same results. ssh service wont start.
thanks!
rp201 said:
thanks for the video and your time. did a new install. stilll same results. ssh service wont start. is privacy guard an app or settings in lineageOS?
thanks!
Click to expand...
Click to collapse
Developer options > manage root access. (Screenshot attached)
But it doesn't matter, I used Kali with SuperSU and magisk and it worked.
Does it tell you something when you tap on RUN on the custom command ?
Quick recap:
1-Flash Lineage
2-root
3-boot and install BusyBox and nethunter app
3-through nethunter app install Kali chroot (it will download the image and mount it in /data/local/nhsystem)
4-Reboot
5-Create custom command to start SSH service
6-Run SSH service
7-Connect to SSH with a client
I also just remembered you can see if the service is up from the nethunter app, check attachments.
LineageOS just updated to 5th june I updated and the chroot still works.
okay so I reinstalled and enabled the use of privacy guard in lineageOS first boot setup. when I go under privacy I dont see any settings to give busybox installer root access. dev-options only has settings to give root access to "enable root adb only" it does not have the usual "enable root adb and apps" any help would be great.
in my previous installs nethunter full not miniimal is installed. I have the ablility to install chroot and remove it. after reboot I would get status bar message like you saying nh service system is up and running. created entry like you the same. Thank you for helping. trying to figure out how to enable root without installing supersu in twrp like you.
rp201 said:
okay so I reinstalled and enabled the use of privacy guard in lineageOS first boot setup. when I go under privacy I dont see any settings to give busybox installer root access. dev-options only has settings to give root access to "enable root adb only" it does not have the usual "enable root adb and apps" any help would be great.
Click to expand...
Click to collapse
Because you didn't root with the LineageOS root zip
But as I said I don't think that's the issue.
I attach you the needed zips, the installer and the remover. Just flash through TWRP instead of using SuperSU.
Then go to developer options and in that menu it will appear more options select apps and ADB (check screenshot in the attachments)
This is just to put you in my same conditions but I don't believe it will fix the issue.
After much help from seanwik and 24 nhinstall.logs...its up and running connecting over ssh. I didn't stop there. After a little playing I got nhterm to work with Kali term instead of suandroid. Found a setting in dev options. Still does not launch within nethunter but I'm working on it.
I remember reading you have to uninstall nhterm.apk nh.apk vnc.apk and install nhterm vnc then nh in that order. Some of my playing included manually installing all the nh.apks from the nh.zip using xplore .
Nhterm
rp201 said:
Nhterm
Click to expand...
Click to collapse
Glad it works, but I'll stick to JuiceSSH because I love the interface and it's features. And since I use for remote accessing my servers it's much easier for me to have everything in the same library ?