Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
chicojd said:
Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
Click to expand...
Click to collapse
Do a search for an Ubuntu SDK guide, there's a really good one floating around. You need to create a couple of text files to get it to register the USB device, the guide tells you how to do that.
Search for ubuntu udev android. You should be able to find it that way...
Related
I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
phenixdragon said:
I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
Click to expand...
Click to collapse
Once you have the usb drivers installed correctly, and have adb/fastboot/etc added to you system PATH, then in a command prompt type "adb devices". If it shows your device ID, then you have adb working correctly. Otherwise, you should check to make sure usb drivers are installed correctly. If it did work, then type "adb" and it should list most of the commands. Most common ones are: "adb remount", "adb shell", "adb lolcat", etc.
Also, for future reference, please post in the correct sub forum
I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?
I use Debian and my command is adb start-server.
Give it a try.
Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help
Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??
Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.
I am using my laptop for ADB currently, but I want to know if it is possible to run ADB through windows in a Virtual Machine? I have gotten to where I have ADB running and the VM reconizeds the phone but as soon as I type,
Code:
adb devices
There is no response. Side note: I am using VMware and am running Tvall's CM7 on my phone.
Edit: solved was a driver issue
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
5[Strogino] said:
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
Click to expand...
Click to collapse
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
acseazzu said:
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
Click to expand...
Click to collapse
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
5[Strogino] said:
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
Click to expand...
Click to collapse
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
How did you fix it?
acseazzu said:
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
Click to expand...
Click to collapse
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
kazzarok said:
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
Click to expand...
Click to collapse
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
acseazzu said:
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
Click to expand...
Click to collapse
I am using Oracle VM Virtualbox. Doing VM Windows 7 under Ubuntu 11.10.
I have been trying a few times in the VM Windows 7. I tried the lastest HTC Sync 3.0.0.0 as well as the older version 2.0.3.3 that worked when I was using full Windows 7.
But in VM, nothing works
The VM win 7 can detect a USB Composite Device, but it cant find the correct driver.
edit:
Oh my god!! hopefully you still havent read this post yet because I just got it working!
In the settings of the VM, theres an option to enable USB 2.0
But to enable that, we must install the Oracle VM VirtualBox Extension Pack
It works!
edit2:
but somehow the transfer speed is really slow...
i guess i will just install windows again dual boot it
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
acseazzu said:
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
Click to expand...
Click to collapse
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in adcance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
kazzarok said:
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in advance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
Click to expand...
Click to collapse
I personally use Workstation. But for me VMware is alot faster than Oracle VM VirtualBox. Glad I could help
adb driver won't connect
I'm running windows parrallel on my mac. On the windows side I have the samsung drivers downloaded but when I go to root my phone the command line says doesn't recognize. Anyone know away I can get drivers to recognize phone when running virtual on a mac?
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
im trying to load into adb but it won't find the device, usb not reading. can anyone help?
the_rorshach said:
im trying to load into adb but it won't find the device, usb not reading. can anyone help?
Click to expand...
Click to collapse
You need the Samsung USB drivers installed first and the adb binaries on your PC.
Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.
the_rorshach said:
Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.
Click to expand...
Click to collapse
You can download the adb binaries as part of the Google platform tools package.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open a command prompt from within the folder where the adb binaries are.
Gotcha, just got issues on win 7