Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Waiting for phone to connect galaxy s3 #6

unixndata opened this Issue Oct 6, 2012 · 8 comments


None yet
4 participants

Hey mate,

Installed it as your post etc and i load it up and it keeps saying waiting to connect...

I have tried IOS devices and android but i always get waiting for phone to connect, is there an issue with the s3's ?



kosborn commented Oct 6, 2012

I need a little more info. What device is it loaded on? Are all prerequisites met (root, busybody, running it as root, have a USB OTG cable, etc). Is the device you're connected have adb enabled? p2p-adb doesn't do anything against iOS devices.

Phones running root, busybox, 4.0.4 android has su priv's, the device's I tried where factory android devices. I tried to get the gallery of the other phone has per your hak5 video to no avail either, is there a trick to it ? mtp is enabled on my s3 and i connect to the ios and it just charges it etc. also have USB OTG cable.



darKpoiSon commented Oct 6, 2012

had this problem aswell.. I don't know if its on every phone, but on the Galaxy S3 adb is always running. The problem is, it's not running as root, but it has to.
So either stop and start the adb server manually using:
adb kill-server
adb start-server

or write in in the functions.sh script.

I would change the script to automatically stop and start the adb server. It doesn't take that long, but you're sure it's running as root

Same issue if not running as root. Fixed by killing and relaunching with su (or sudo) !
Maybe just should be added in the script start.
I'm working on a platform switch (launched on a phone/a computer) :

  • Busybox ON/OFF
  • adb path + su (or sudo)
  • Little gui on computers ?

Will it be useful ?


yeah it would. Will try this out as soon as i can.



kosborn commented Oct 6, 2012

ADB server running without root privs appears to be a common issue. I'll address it with adb kill-server and su -c 'adb start-server'. That should be sufficient to solve most problems.


kosborn commented Oct 8, 2012

@Hackrylix About a switch for desktop, what's the point exactly? The code should run fine on just about any vanilla linux install with adb. Busybox can be disabled manually in run.sh. Also, I will not officially support any GUI for any machine (android, linux, os x, windows), so I can maintain compatibility, and size, of the project. It already bums me out that I've had to include binaries in the project, but it's a necessary evil).

You can fork/create a new project that contains the GUI, and I encourage it. I'm even working on making it easier to dynamically generate a list of modules and going to build a wrapper specifically for a GUI (I actually would really like an Android GUI utilizing this soon to be pushed method.)

@kosborn kosborn added a commit that referenced this issue Oct 8, 2012

@kosborn kosborn Added reference to issue #6 14240db

@kosborn kosborn closed this Oct 8, 2012

@kosborn kosborn added a commit that referenced this issue Oct 8, 2012

@kosborn kosborn Added reference to issue #6 3b569a5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment