Related
I need a bit of help installing my Android G1 USB drivers included in the Android SDK.
When I attach my Android G1 to my pc, it doesn't ask to search for drivers to install. I believe it automatically installs the drivers, as I see "HTC Android Phone USB Device" in device manager. Though that shows up, when I check for attached devices via ADB "adb.exe included in sdk ( SDK\Tools\adb,exe )", it doesn't list my device.
What should I do from there?
PS: Is there any other application that I need? Is eclipse required.
Note: My Android G1 is unactivated ( I am trying to activate without Sim or data plan [ Via Wi-Fi I guess? ])
You need to go to the development option and check on USB Debugging, but I think you your problem is you have to download the android_usb_windows.zip for adb to see your device.
I have the USB Drivers, the issue is probably the fact that I don't have eclipse.
Maybe I should download it, yes?
{{ What ver. of Eclipse? Java EE or Java? }}
Eclipse is not required. Heck, the full sdk is not even required. There is a zip file floating around that is just adb.exe and adbwin.dll. Works fine.
In that case, how do I enable Device debugging.
I downloaded the SDK (includes adb)
where should I set the usb drivers and how do I enable them?
settings->Applications->Development->USB debugging
JesusFreke said:
settings->Applications->Development->USB debugging
Click to expand...
Click to collapse
i have done it
but still cant setup usb driver correctly.
rddhome said:
i have done it
but still cant setup usb driver correctly.
Click to expand...
Click to collapse
what instructions are you following?
go under device manager and check under universal serial bus controllers...its prolly listed under usb mass storage device. you gotta go find the correct one and install the drivers manually. also you gotta type in that setprop.blah blah nonsense on your g1 and the computer will recognize it. check the ADB setup for dummies thread
rddhome said:
i have done it
but still cant setup usb driver correctly.
Click to expand...
Click to collapse
i have code 10 error for adb interface/htc dream composite adb interface in device manager.
volcomnator999 said:
go under device manager and check under universal serial bus controllers...its prolly listed under usb mass storage device. you gotta go find the correct one and install the drivers manually. also you gotta type in that setprop.blah blah nonsense on your g1 and the computer will recognize it. check the ADB setup for dummies thread
Click to expand...
Click to collapse
thankful.
i finish it following as u said.
but what reason?
I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it
TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.
As per title...
If your rooted, use an app like 'ShootMe' that you can get from the market for free, and then you can take screenshots on the move.
otherwise install the android SDK and use DDMS which can be sound under 'tools'
connect your device and choose 'Screen Capture'
Could yo advise where I find the android SDK?
you can also use these easy tools here
http://forum.xda-developers.com/showthread.php?goto=newpost&t=765081
AllGamer said:
you can also use these easy tools here
http://forum.xda-developers.com/showthread.php?goto=newpost&t=765081
Click to expand...
Click to collapse
The manager tool does not take screen shots and the ADB one requires Root.
otherwise install the android SDK and use DDMS which can be sound under 'tools'
Click to expand...
Click to collapse
So where do I get this ?
a simple google of what you want
android sdk
returns this as first result.. http://developer.android.com/sdk/index.html
if ur not comfortable with this, or rooting your device, then your out of luck
note: adb doesnt require root, im not sure what your on about
the ADB for non Geek doesn't require root
ShootMe needs root, but is easier to use
sensi_ said:
a simple google of what you want
android sdk
returns this as first result.. http://developer.android.com/sdk/index.html
if ur not comfortable with this, or rooting your device, then your out of luck
note: adb doesnt require root, im not sure what your on about
Click to expand...
Click to collapse
From the ADB link page
it requires installed AndroidSDK and busybox on phone (so and root)
Click to expand...
Click to collapse
Got the SDK and running now though it was a little in depth to install for a noob. Posted some desktop pics as well so thanks to all who helped.
Sorry folks, this just doesn't cut it.
I am not a newbie to computers. I've been using them for about 25 years now.
Someone's got to come along soon and write a simple app that anyone can download and run AS IS. No special Android development software required or rooting etc.
A simple app that takes screen shots, period.
One that won't void your Samsung warranty.
i use linux on my home pc and i have not seen a thread or qestion answered about flashing odin from linux so i tried it myself, forgive me if it has been covered before.
i was able to successfully flash with odin using windeows running inside a vm. my vm software is sun virtual box.
before you do this read the instructions for running odin in widows as i dont go into odin specific detail here.
1. created virtual machine.
2. installed windows XP sp2 on virtual machine
3. installed the newwest version of .net framework(i read that helps but it may have been in reference to kies)
4. dowloaded odin and the proper windows drivers and .pit file and jh2
5. shut down the virtual machine
6. put phone into download mode
7. plugged phone into usb port
8. went into virtual box without the VM running and select
machine>settings>usb
9. clicked the add device icon on the right and clicked on samsung_android[0400]
10. started virtual machine
11. started odin and added the proper .pit file and .tar file
12. pulled batery from phone and put into download mode again and connected the usb and selected devices from the top of the window, selected "samsung_android [0400]"
at this point odin should see the device. if not you may need to reselect the phone in the vm window, do this quickly as there seems to be a time window to start the conection.
simply click start!
this may work in vmware and other vm type software for mac and linux as long as you can mount usb devices to the vm as soon as they are hooked up. if it can be done by com port and not device that may be even better.
i have only done this with virtual box 3.2 running widows XP inside mint 9
if it fails i am not responsible for damage to your device. and in the event it doesn't work go find a friend with windows and run it the proper way! windows machines aren't hard to find!
this worked for my iphone with itunes but was trickier as the driver changes halfway through and that is why i thought this would work.
wine does not work, i have not been able to use wine with software for any device that need drivers when running in widows. so please dont ask!
Not running Linux except for my G1 theme dev,but thanks for the info.
Sent from my SAMSUNG-SGH-I897 using XDA App
I can verify VirtualBox works great for this. Qemu didn't, afaict none of the host USB access options work as documented.
Vmware also works perfectly.
Sent from my GT-I9000 using XDA App
Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.
I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.
ponack said:
Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.
Click to expand...
Click to collapse
wine will not work. it doesn't support USB plugging
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Click to expand...
Click to collapse
Yeah, I figured that out after I posted - I was like wait, there's drivers that need to be installed. Oops.
Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Couldn't have said it better, I have tried wine with lots of software but never got the usb end of things to work. Odin does open under wine but I have no idea how to tell it to see the phone as it would see a windows driver that sees the phone.if that makes sense.
There are things I can try but if feel I'd be wasting my time as I don't know enough to be sure I'm on the right path.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
TimF said:
I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.
Click to expand...
Click to collapse
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Dani897 said:
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...
pietro_spina said:
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...
Click to expand...
Click to collapse
well I can see it in download mode now... It was just the stupid front ports on my computer. Seems to prefer the back ones...
so now a device is visible in my windows VM but it is called "Gadget Serial"
When it is in "recovery" windows VM can see it as Samsung etc.. and Odin can connect... But obviously odin needs it to be in "download" not "recovery" for it to work.
I've problems trying it...
In normal mode all works and VM detects correctly...
But when I put the phone in Download Mode, "lsusb" freezes...
any ideas?
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.
Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
mystichobo said:
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.
Click to expand...
Click to collapse
this thread was risen from the dead.....
for no reason as you have mentioned. look at the date of the OP, and realize that heimdall wasnt always available
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.