[Q] [510] AndroidVNC and Terminal Emulator - Acer Iconia A700 and A510

Hi everyone,
my A510 is driving me crazy.
Here is what I’m trying to do:
I want to run Ubuntu and connect to it with AndroidVNC.
I emulate the Ubuntu with Terminal Emulator and it is running fine without any errors.
I go back to the Homescreen and open AndroidVNC. I fill in the necessary fields and hit connect.
And instantly I get this error message:
Code:
Error!
VNC connection failed!
Failed to connect to /127.0.0.1 (port 5900): connect
Failed: ECONNREFUSED (Connection refused)
I tried to connect with Jump and basically the same result. I tried different ports or “localhost” instead of I.P. I used a different emulator and no success.
I also tried different ways to run Linux but none of them solved my Problem.
The androidVNC itself is running fine. I can connect to my Laptop (TightVNC Server running on it) via WLAN and control it.
The only thing it won’t do is connect to the Linux running on the Terminal Emulator.
Do you have any ideas or hints on how to solve the problem?
Android Version: 4.0.3
Kernel: 2.6.39.4+ (stock)
Tablet is rooted – Busybox and Superuser installed
Regards
Rix

Found this interesting and tested it on my A700.
The vnc password is "ubuntu" even if you set a different one on first start.
In the terminal window must show up the line "New 'X' desktop is localhosr:0" after you entered the screen size.
Now I can connect via VNC. I use "ubuntu" as nick, password and username. IP is "localhost".
Hope these few hinty may help.
Sent from my A700 using xda app-developers app

Thanks for your reply.
I have reset my Tablet to factory settings and rooted it again.
Installed Terminal Server and AndroidVNC. Emulated Linux and again the same result.
I don't know why it does not want to connect to the localhost.
My settings are exactly as in the description(s).

Did you use the image provided by this app: https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid ?
This worked for me, even if the result is not very usable. Must figure out, how to use a different window manager, the default one is missing some graphics and has problems with the launchbar icons.

Tried this one as well. No success.
I just don't get it. The device is properly rooted with the "one click" version. Root check tells me it is rooted.
Busybox is succesfully installed. The Linux is running in the emulator but i just can't connect to it.
The strange thing is:
The error message is the same, whether I fill in the fields in AndroidVNC or not.
It absolutely refuses to connect to 127.0.0.1 or localhost.
Really frustrating....

Did you check if the vnc server is really running?
"ps -a" should show a "Xtightvnc" process.
Sent from my A700 using xda app-developers app

OK. I don't know why, but all over sudden it works.
The only thing I need to do know is install a VPN Client using IPSec. Challenge accepted.

Rixar said:
OK. I don't know why, but all over sudden it works.
The only thing I need to do know is install a VPN Client using IPSec. Challenge accepted.
Click to expand...
Click to collapse
hey buddy, i am having the exact problem with my VNC and TF201, the terminal is running though can NOT connec to the GUI mod, could u help me out ?
Amir

AmirJamez said:
hey buddy, i am having the exact problem with my VNC and TF201, the terminal is running though can NOT connec to the GUI mod, could u help me out ?
Amir
Click to expand...
Click to collapse
did you ever solve this? i have everything setup but the vnc wont let me connect

DЯΦ[email protected]П said:
Found this interesting and tested it on my A700.
The vnc password is "ubuntu" even if you set a different one on first start.
In the terminal window must show up the line "New 'X' desktop is localhosr:0" after you entered the screen size.
Now I can connect via VNC. I use "ubuntu" as nick, password and username. IP is "localhost".
Hope these few hinty may help.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much man!!! i knew it was a simple thing. IP "localhost" PW "changeme".
I killed myself looking for this answers. Kali installed and running on VNC.

Related

ADB USB Driver

the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.
Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.
I have the same problem... working on it now...
I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.
It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Thank you dagentooboy!
Can someone explain this for this not so savvy person?
chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.
Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.
yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.
Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..
check too make sure your Android isnt listed under usb mass storage devices in device manager.
Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.
my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this
Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...

[APP] dropbear ssh client for razr i

Compiled with android-x86 cross-tools. It's a binary you need to push with adb.
Source code is from https://github.com/CyanogenMod/android_external_dropbear.git , so credit to CM teams.
INSTRUCTION
adb remount
adb push ssh /system/xbin
Maybe you need to check the permission/owner stuff with a shell.
Forgive me for my ignorance, for what is this?
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
Marco Lomas said:
Forgive me for my ignorance, for what is this?
Intel device - Razr i Owner
Hit thanks if i help you or you like my style
Click to expand...
Click to collapse
If you don't know what ssh is, then you hardly need this app.
It's a command line program used to connect to Unix/Linux server with ssh protocol.
Setarcos said:
If you don't know what ssh is, then you hardly need this app.
It's a command line program used to connect to Unix/Linux server with ssh protocol.
Click to expand...
Click to collapse
Well i read about it, its about like remote operation whit commands....sounds cool
Ty for your work . Maybe sometime i will use it
Intel device - Razr i Owner
Hit thanks if i help you or you like my style

[Completed] [Q] Linux Deploy Help

Hi, I have successfully installed Kali Linux on my LG G3 using Linux Deploy and VNC viewer. I am successfully able to use everything, but I am relatively new to Linux. Still, I was able to switch to root in the terminal. I also tried creating a new account, giving it root access, and then switching to it, which I was able to do, again only in the terminal. However, even if I had root access in the terminal (confirmed by "whoami"), it seemed that I did not have any other root privileges. For example, everything, including the desktop, was read only. I tried switching users using the gui and that did not work at all. I also tried to open the root folder under computer and I wasn't able to do that either. I have tried changing the preferences in linux deploy to log me in as username "root," but I think even then I am logged in as a user that is named root... not the actual root administrator. If anyone could offer some guidance with this situation that would be great. I have spent a lot of time searching google and more to find the solution to this problem, but I haven't had any success. Thanks in advance.
I'd also like to add that some normal commands were not accessible in the terminal even though it said that I had root privileges. Therefore, I could not get done what I would like to even if I were to do everything in the terminal .
jackfitz5 said:
Hi, I have successfully installed Kali Linux on my LG G3 using Linux Deploy and VNC viewer. I am successfully able to use everything, but I am relatively new to Linux. Still, I was able to switch to root in the terminal. I also tried creating a new account, giving it root access, and then switching to it, which I was able to do, again only in the terminal. However, even if I had root access in the terminal (confirmed by "whoami"), it seemed that I did not have any other root privileges. For example, everything, including the desktop, was read only. I tried switching users using the gui and that did not work at all. I also tried to open the root folder under computer and I wasn't able to do that either. I have tried changing the preferences in linux deploy to log me in as username "root," but I think even then I am logged in as a user that is named root... not the actual root administrator. If anyone could offer some guidance with this situation that would be great. I have spent a lot of time searching google and more to find the solution to this problem, but I haven't had any success. Thanks in advance.
Click to expand...
Click to collapse
There is not a specific XDA forum for Kali Linux.
You might find some help in Ubuntu Touch General
or [APP] Linux Deploy by AbuYahya
Which S3? SGH-I747 or I9300, I9305 ...

help with nethunter and mulitrom

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 ?

Android X86 -> Proxy Setting?!

Hi
I Installed Android x86 on an Virtual PC. Its Version 6.1.4 I guess. Everything run fine. I can access Local Pages. But I dont finde any Info where I have to config a Proxy Server?! There is no Settings for! Are there any command Line thinks I can hack in to set an Proxy for all Application?
Thanks!
I_AGREE_BUTTON said:
Hi
I Installed Android x86 on an Virtual PC. Its Version 6.1.4 I guess. Everything run fine. I can access Local Pages. But I dont finde any Info where I have to config a Proxy Server?! There is no Settings for! Are there any command Line thinks I can hack in to set an Proxy for all Application?
Thanks!
Click to expand...
Click to collapse
Open a Terminal Emulator and then su and then run the following command:
Code:
settings put global http_proxy <PROXY_IP>:<PROXY_PORT>
thanks I will try tomorrow. Maybe I tried and the didnt work but I will try tomorrow morning.

Categories

Resources