Related
i have an idea for an application to remotely control a daemon on my desktop through a telnet connection. i can connect to the daemon through normal telnet methods (locally and connectbot), but can't operate the daemon through koushik's raw telnet client or the java code from inside eclipse.
the code that i have written so far can establish a connection, but pauses/freezes/stops after the socket is opened. no input or output is transferred. examining the tcp packets in wireshark, i've come to the conclusion that the connect method i'm using (org.apache.commons.net.telnet.TelnetClient) doesn't send WILL_ECHO to the host, and that keeps the daemon from finishing the connection -- at least, the failing connection methods stop (read: it's not there) at this packet while the working connection methods have this packet and everything after. it exhibits the same behavior using both my java code and koushik's telnet client, so i don't think it's anything i've written, rather, i think it's something i haven't written.
what i'm looking for is a bit of help in getting java connected to the daemon. if i can get the code to connect from eclipse, the rest should be a snap. if anyone has been able to get a telnet connection established using java, the android sdk, or just plain-old knows more about TCP than i do, i would appreciate some pointers - actual code examples, ideas, nudges, or where to go for deeper information.
attached are plaintext packet captures of what i have. the first is from the java code (inside eclipse) to the localhost daemon showing the fail, the second is from connectbot on the phone to the same daemon showing a working connection.
- tasker.
Try using just a raw socket. Telnet daemons don't care what connects to them typically and you can send commands and such with a socket without issue. I've done it in regular Java before, unfortunately it was for work so I can't share code. The basic examples in the javadocs should work though.
Figured out what my problem was.
after it connected my code was waiting for a character that never came, thus leaving the InputStream open and not doing anything else. Adjusted the string that it was waiting for and BAM! -- it worked.
Just found this. Works great. Install this on your phone, http://code.google.com/p/android-notifier/downloads/detail?name=AndroidNotifier-0.2.4.apk&can=2&q= and this on your PC (Windows/Linux) http://code.google.com/p/android-notifier-desktop/ or this for Mac http://code.google.com/p/android-notifier/downloads/detail?name=MacDroidNotifier-0.2.6.dmg&can=2&q=
For users who need a guide in setting up the application may visit the following web pages:-
- http://droidbar.net/2010/09/setup-guide-on-remote-notifier-for-android-via-wi-fi-windows/ (Connect via Wi-Fi on Windows)
- http://droidbar.net/2010/10/setup-guide-on-remote-notifier-for-android-via-wi-fi-ubuntu-linux/ (Connect via Wi-Fi on Ubuntu Linux)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-windows/ (Connect via Bluetooth on Windows)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-ubuntu-linux/ (Connect via Bluetooth on Ubuntu Linux)
Should also note that to use the 64 bit version of the windows software you must be running 64 bit java.
Now this is just awesome.
However it needs a fair bit of setting up in Windows as the balloon notifications are ugly.
Maybe I'll try Growl for windows!
I have had this for about 2 weeks now. The latest update is becoming annoying because it gives me a battery notification every 5 minutes. Maybe its the rom im using.
I cant seem to get this working. I would assume that since my desktop is connected to the network via Wired Connection, and my phone via wifi, but my pc wont see any of the services.
[edit] turns out i had to set it to sent to my custom IP and it works
I just saw this and downloaded it... It's perfect for me!
It worked perfectly first time, no configuration needed... just start the app and start the .exe on my PC and it works great.
One question I do have though is, what is Growl and how do I get it?
ya, i set up custom ip, which i assume would be the ip address of my desktop? and no go for some reason. too bad, i could actually use this. any suggestions would help but if not, Ill try and email the dev..vista with a wired connection to my router, if that makes a difference
bbrosen said:
ya, i set up custom ip, which i assume would be the ip address of my desktop? and no go for some reason. too bad, i could actually use this. any suggestions would help but if not, Ill try and email the dev..vista with a wired connection to my router, if that makes a difference
Click to expand...
Click to collapse
Try double checking your IP address?
Control Panel > Network and Internet > Network and Sharing Center (If you're on Windows)
1. Click on "Local Area Connection" (If you're on Wired Connection)
2. Click on "Details..."
3. Look for your IP address at "IPv4 Address"
However, if the IP address of your desktop is not static. I’m afraid it will vary whenever you reboot your router/modem.
Alternatively, you may set the Target IP address to “Global broadcast address” on your phone.
ADeadlySpoon said:
I just saw this and downloaded it... It's perfect for me!
It worked perfectly first time, no configuration needed... just start the app and start the .exe on my PC and it works great.
One question I do have though is, what is Growl and how do I get it?
Click to expand...
Click to collapse
http://www.growlforwindows.com/gfw/default.aspx
Just install that, pick a nice display, then go in android-notifications and enable the Growl and disable System default.
Does not work for me using windows7
Downloaded client..run ...SAVE..send test ping.. nothing happen
Im sure ma phone and PC are in same network.Firewall is disabled.
Some ideas?
castaway1 said:
Does not work for me using windows7
Downloaded client..run ...SAVE..send test ping.. nothing happen
Im sure ma phone and PC are in same network.Firewall is disabled.
Some ideas?
Click to expand...
Click to collapse
Are you on 32-bit or 64-bit Operating System (OS)?
Did you download the 32-bit or 64-bit client for Android Notifier Desktop onto your desktop?
If you're on 64-bit OS and downloaded the 64-bit client for Android Notifier Desktop, you also need 64-bit Java.
Additionally, is the Target IP address set to “Global broadcast address” or "Custom IP or host" on your phone?
If it is on "Custom IP or host" you need to manually add the IP address of your desktop to it.
For users who need a guide in setting up the application may visit the following web pages:-
- http://droidbar.net/2010/09/setup-guide-on-remote-notifier-for-android-via-wi-fi-windows/ (Connect via Wi-Fi on Windows)
- http://droidbar.net/2010/10/setup-guide-on-remote-notifier-for-android-via-wi-fi-ubuntu-linux/ (Connect via Wi-Fi on Ubuntu Linux)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-windows/ (Connect via Bluetooth on Windows)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-ubuntu-linux/ (Connect via Bluetooth on Ubuntu Linux)
Android-notifier and DHCP networks
Does anyone have any clever ideas on how to get the following to work:
DynDNS hostname used on home network.
Router set to forward packets on the proper port.
I'd like it if I could forward to the broadcast address rather than a fixed IP. I.E., it doesn't matter WHICH computer receives the broadcast after it gets to my home network, just that SOMETHING does.
(I can't guarantee which computer I'll be using)
Ideally, I'd also like to be able to use this on my laptop, regardless of where I am: home or elsewhere, tethered or not.
make sense?
I can't keep a constant wireless connection on my nexus one but it works as long as the wireless doesn't hang which never happens...
so I tried to get Bluetooth working, I fainally got able to pair with my PC (Windows 7 64bit.) And it says paired but not connected on the phone. I try to send the test notification from the phone, but never got anything on the PC.
Can this work over the internet?
kristopherson said:
Just found this. Works great. Install this on your phone, http://code.google.com/p/android-notifier/downloads/detail?name=AndroidNotifier-0.2.4.apk&can=2&q= and this on your PC (Windows/Linux) http://code.google.com/p/android-notifier-desktop/ or this for Mac http://code.google.com/p/android-notifier/downloads/detail?name=MacDroidNotifier-0.2.6.dmg&can=2&q=
Click to expand...
Click to collapse
Link for Windows/Linux download is broken. Please fix or remove, thanks!
You got it here:
code.google.com/p/android-notifier/downloads/list
thnx anyway ,, but it didn't work for me
403. That’s an error.
Your client does not have permission to get URL /p/android-notifier-desktop/ from this server. That’s all we know.
can anyone upload it?
here
locknes said:
403. That’s an error.
Your client does not have permission to get URL /p/android-notifier-desktop/ from this server. That’s all we know.
can anyone upload it?
Click to expand...
Click to collapse
http://code.google.com/p/android-notifier/downloads/list
If someone got the IP and port you use for wireless adb, could they hack your phone, if you had the service running
Don't you need to run this via a computer, of which you would need to be on that networks wifi, which is hopefully password protected.
What are the changes someone hacks into peoples wifi and starts running adb devices in hopes of getting access to an android phone...
blas4me said:
If someone got the IP and port you use for wireless adb, could they hack your phone, if you had the service running
Click to expand...
Click to collapse
hack, like with an axe ?
ohhh, you mean open a shell, with root priv's... i'm actually not going to lose any sleep over it... being that Windows Phone 7 is going to 'dominate', 'terrify', and 'obliterate' android in the coming weeks of holiday sales.
or something
Nothing is impossible
Private networks get hacked, I just want to know if it's possible. I'm not sure that's why I'm asking.
Wireless ADB is an open shell without security.
Of course, if anyone connects, he can do anything with your phone that ADB allows. It's not called "hacking".
There's absolutely no reason to run ADB service unless you're actively working on your phone.
Private networks that are penetrated have crap for basic security. WPA can't be broken for half a decade, and with key change interval below 13 min it can't even be poisoned.
Hello all I have been using a captivate for some of my dev work and all was going well but just today I can no longer see it in my devices using ddms or adb devices.
Looks like adbd is running on the phone and I can mount the sd card fine. I tried in two machines, one mac and one windows... So its something in the phone and a factory reset didn't fix it - any tips on how I should go about troubleshooting this?
It was working fine so I am a bit miffed.
Thanks so much
Jit
--
Sent from my SAMSUNG-SGH-I897 using XDA App
Still not working with a mac
All:
Just an update to the issue - the Captivate still refuses to be recognized by ADB, although it works fine on the same machine when I boot into Windows and use Samsung Kies.
On the Mac side, I can mount the files when USB debugging is on by going to the USB status icon and selecting Mount storage. The Mac even recognizes the connection as a new network connection (although I simply ignore that part). So looks like the USB subsystem on my Mac is somehow not recognizing the ADB communication. I upgraded to android release 8 and still the same problem.
Is there a way to completely reset the USB subsystem on a Mac without having to reinstall the OS?
Thanks so much - the weird thing is that the captivate worked okay for a week or so before deciding not to work with adb any more - I can still generate apks and sideload the apks into the device but I would really like to be able to do some on-device debugging.
Thanks so much for any help that you guys can give.
Jit
Edit: Nevermind
SOLVED - ADB Issue with Captivate
All:
After quite a bit of research finally figured out why ADB will not recognize the captivate (or for that matter any other android device). The problem was because I had installed EasyTether. Its a pretty nice software and pretty easy to use to tether android devices, unfortunately it kills adb's usb capabilities.
I found this issue in EasyTether's FAQ area so if anybody else is having the same problem you will need to unload the EasyTether Kernel Extension (unfortunately that didn't totally fix the problem for me - I kept losing communication intermittently so I ultimately removed Easytether from my mac as well as from the Captivate and now I can see the device in adb again).
Just thought I would share the solution with the rest of the very helpful community.
Jit
4th Update 5/2/2013 - Found a bug... Nothing that would affect the overall functionality, but it could cause some users to think that their phone is successfully connected via USB debugging, when it really isn't.
Update: 5/2/2013 - Per user requests, adding link to VirtualBox download site on the original post.
3rd Update 5/1/2013 - I changed the code that 'finds' the exploit file to make sure it get executed successfully. It's now using the "PATH" environment to do this. This is more reliable than the actual Linux 'find' command I was using before. Also added some additional instructions to clarify some steps based on feedback from users. Finally, added code to detect if the network adapter is not configured correctly. It will alert the user to configure the network adapter properly in the VirtualBox application.
2nd Update 5/1/2013 - I added some lines to the script to stress the importance of pressing one of the three hardware buttons on the phone (Volume up, Volume Down, or Power) once the exploit has been executed. After discussing this with the author of the exploit, this is an important step to obtaining root.
UPDATE 5/1/2013 - New and improved .ova file. Contains improved logic in the exploit script to help with some of the problems that have been encountered by users.
If you've had trouble rooting, please download the new version and try again!
Hey folks, I'm a UNIX admin by profession, so I took the challenge over the weekend to come up with an easy root process for Bionic stock Jelly Bean, specifically for those who aren't familiar with Linux.
I decided to build a Linux VM under Oracle VirtualBox on my Windows PC. This seemed like the logical choice since VirtualBox is free, a relatively small download, is easy to install and it's easy to import VMs.
My first attempt was using CentOS Linux. It worked, but the file required for users to download was over 450MB... Back to the drawing board!
Started looking for very small Linux distros and found Tiny Core Linux. This worked well. The file required for download is 50 MB.
Everything you need to root the Bionic is here and it is automatic. The process will walk you through connecting to the Samba file share, connecting the phone in USB debugging mode, and OF COURSE, it will run the process to root the phone.
Here are the steps:
1) Install Sun VirtualBox on your Windows PC.
http://download.virtualbox.org/virtualbox/4.2.12/VirtualBox-4.2.12-84980-Win.exe
Note: We've had one report that this file also works with VMWare Workstation and VMWare Player. If you don't want to install VirtualBox feel free try the file with VMWare.
2) Download the VirtualBox .ova file containing the Linux VM from one of the following links:
http://www.knite.net/Bionic/Root_Bionic_JB_20130501-4.ova
http://www.mediafire.com/?a2i6forosp77xrd
https://dl.dropboxusercontent.com/s...fhiAIiSwc0jD1AdVFNY27QdoeKP9ot_7IdDetSvw&dl=1
3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)
4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)
5) Follow the instructions on the Linux console.
That should do it. If you need help I will be monitoring this thread.
Willing Tester
I am not familiar with Linux but I am familiar with root, supersuser, recovery, and fxz/rsd lite. I am up for a new phone next month so I am willing to try this on my Bionic. This doesn't sound too hard....(famous last words). Will try on my Windows 7 laptop.
Will report if this works. Won't be able to until later today.
Thank you OP!
Found a problem with the script. Should work now. Download and import again, if you've already downloaded. I also managed to get the download down to 46MB by defragging and compacting the .vmdk file.
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1
Downloading new link now. Haven't tried to root yet. I'm at work right now.
Do you have any other suggestions before I start? I don't have to be completely stock do I...? (all stock apps, no superuser, etc.) I am on stock jelly bean 4.2.1, ver. 98.72.22.XT875.Verizon.en.US, stock recovery...but I did use OTA Rootkeeper so I have a (semi-functioning) superuser install. Do you suggest starting fresh with fxz?
I will be home in a couple hours to give it a try.
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Great, I just wanted to do something to make it easier for everyone, since so many seemed to be struggling with Linux.
lc75 said:
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Click to expand...
Click to collapse
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
TechnoHippie said:
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Click to expand...
Click to collapse
marty45714 said:
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
Click to expand...
Click to collapse
Ok that's gonna be my problem then ...I'll give it a shot when I get home and I'm not connected to my office network.
USB 3.0?
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
I am struggling with the directions and feeling dumb about it... Not sure what to put for the "Host IP Address"
EDIT: Restarted the virtual machine and it gave me the information I needed. The first time around the field was blank.
I appear to still lack root because the SU app wants to update the binary and fails to do so.
I'm not sure, but one thing you can check. When the Linux console is up in the VirtualBox window, there is a section in the lower, right hand corner of that window that shows a bunch of icons. Click the USB icon and very that you see your Bionic as an option for hardware that is connected to your laptop.
Also, I'm making an assumption that you have the Motorola UBS drivers already loaded on your Windows system before you even started this whole process. Maybe I shouldn't make that assumption???
cakessi said:
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
Click to expand...
Click to collapse
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
MNEman13 said:
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
New link. See original post. I have it on Mediafire now.
dcmcc99 said:
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
marty45714 said:
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
Click to expand...
Click to collapse
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
MNEman13 said:
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Click to expand...
Click to collapse
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
marty45714 said:
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
Click to expand...
Click to collapse
Here are some tips that I posted for someone over on Droid Forums. Hopefully some of this will help us figure out what is going on:
Need you to do some investigation. Run the exploit again. Once your phone is connected to the SMB share and the Linux script verifies the connectivity, press Ctrl-C to break out of the script and return to the Linux command prompt. Make sure your phone is connected to USB. From there execute the following commands and share the output with me:
sudo ash
cd /home/guest/share
./adb.linux shell
(if you execute the above command and DO NOT see this prompt: [email protected]_targa/ $
then you have USB connectivity issues and need to make sure you get your phone successfully connected
to VirtualBox and the Linux VM)
ls -l /storage/rfs0
I want to see the output of the "ls" command to verify that the SMB share is being mounted to /storage/rfs0
This can cause the exploit to fail is it's not.
If you see no output from that command, run this command:
find /storage -name pwn
If you get that far and this looks good. Can you type:
su -
and see if you get a root prompt? A root prompt means your prompt will end with '#' instead of '$' before the cursor.
If you do get this, it could be that your Superuser app is simply broken and need re-installed.
The command that the exploit runs to root the phone, once you get this far is:
/storage/rfso/pwn 1
You can try running that manually and see what happens.
caskieadam said:
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
Click to expand...
Click to collapse