hello all,
i had some small trouble setting up adb for my viewsonic gtab, so once i figured it out i thought i'd share.
so far, this is confirmed working only on windows 7 32 and 64 bit. vista should be the same, but i'm not sure, i'll keep you posted. EDIT: we've confirmed these steps for at least vista 32 and xp 32-bit. there shouldn't be any differences between the 32 and 64 bit systems as far as the instructions go.
most of my information comes from nvidia's tegra site, here. that's a pretty technical-minded page though, so i wanted to condense it.
make sure usb debugging is turned on for your tablet (settings -> applications -> development -> usb debugging)
1. open your device manager (right click My Computer -> Manage -> Device Manager)
if you haven't done anything to set up drivers yet, skip to step 4.
2. find your gtab. depending on your previous attempts, this may be under "Android Phone" at the top (Android ADB Interface, make sure it's your tab and not your phone), or under "Universal Serial Bus controllers" on the bottom (called Android somethingorother. should be at the top of the list.)
3. uninstall it. right click, uninstall. check the box that asks you if you want to delete driver software. i didn't need to use usbdeview to uninstall the drivers, but if you're running into issues on this step try it. usbdeview must be run as administrator, thanks droidjunkie.
it looks like most people should just skip right to usbdeview to uninstall any old drivers. like i said, i didn't have any issues using windows' "delete driver software" option, but apparently i was just lucky. rcgabriel recommends usbdeview, and he knows stuff.
4. unplug, and plug your tablet back in. now your device should be under "Other Devices" near the middle (will have a yellow exclamation icon, called NVIDIA harmony). good.
5. hopefully you have the android sdk installed. if you don't, go find a generic guide on setting up adb and then come back. when you have the sdk installed, you need to run "SDK Setup.exe" from where you installed it and use it to download and install the usb drivers (currently r8).
6. open the "usb_driver" folder in your sdk directory. right click "android_winusb.inf" and open it with notepad or your favorite text editor.
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
8. go back into device manager. right click your tablet, select update driver, and click "browse my computer...", then "let me pick...", then "next", then "have disk"
if you're confused on this step, check this post.
9. browse to your android sdk, under the usb_driver folder, and select the "android_winusb.inf" file.
10. of the three choices, the bottom should say "Android Composite ADB Interface". choose it. click next, and allow the driver to install even though you get a big scary red warning.
11. open a command prompt, preferably in the tools directory of your sdk. type the following:
Code:
echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini"
and hit enter. it will just return a new prompt line.
12. test it out.
Code:
adb kill-server
adb devices
you should see your device's serial number. all is well. congrats.
let me know if i should add or clarify anything here. thanks!
Just in case anyone doesn't know what ADB is:
http://developer.android.com/guide/developing/tools/adb.html
Thank you so much! Great info!
this is great! thanks for the concise writeup
I had trouble too. I was unable to get uninstall device to work and put the device under Other devices. I was advised to use usbdeview from pershoot. I used this program to remove the device and was able to get it moved to Other devices in Device Manager.
HTH
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
THANK YOU!!! after trying many different guides this one worked...other then the fact that I had to right click usbdeview and click "run as administrator" in order to delete the driver it keep installing when i would plug in my tab. I am on windows 7 32 bit, for anyone else having problems getting adb working that is using windows 7.
Thanks
I am finally connected via adb.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
I had the same experience on Windows 7 that you are having now. Like you, I tried following all the instructions similar to the ones listed above plus advice from other forums and still could not get it to work. I was finally able to get mine working after I discovered Windows still had some drivers from previous failed attempts stored in its system files. These old drivers were interfering with the proper installation of the new usb driver.
To get rid of the old drivers completely, do a file search for the file named android_winusb.inf in your Windows/System32/DriverStore. If your search results show several file folders with the same driver, try to delete each of the those folders completely. After those folders are deleted, you can do a clean install following iammuze's instructions.
NOTE: To delete those folders you will have to change the folder permissions. It won't be easy to do, because Windows doesn't like having its system files messed with. Unfortunately, I can't give you exact instructions on this, because I don't currently have a Vista machine.
rlapela said:
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Click to expand...
Click to collapse
where does your gtab show up under device manager?
Thanks, it worked great! ADB screen shots!
Look at this mess I have crammed onto one page.
[UPDATE: Problem solved: I had two versions of adb in my PATH and the old version (1.0.20) was being executed instead of the new version (1.0.26). Apparently the old adb silently fails and returns no devices when used in conjunction with the current drivers. I worked this out by accident. But if you're looking for ideas, there are lots in the ADB for Dummies thread: http://forum.xda-developers.com/showthread.php?t=502010 ]
Hi All
I've been banging my head against this for hours with no luck. I can't get adb to recognise my gTablet. Here's what I've done:
I'm on WinXP. gTablet is running zTab Clean 3.0
- I've downloaded the latest ADB USB drivers using the Android tools (driver verion 4.0, December 12 2010).
- I've made the modifications to android_winusb.inf noted above.
- USB Debugging is enabled on the gTab
- adb_usb.ini contains a single line containing: 0x955
I've followed various instructions and the driver install ~seems~ to go ok, but adb doesn't work.
Windows Device Manager lists the following devices which are associated with NVIDIA Harmony:
Android Phone > Android Composite ADB Interface
Universal Serial Bus controllers > USB Composite Device
Universal Serial Bus controllers > USB Mass Storage Device
USBDeview lists three devices:
NVIDIA Harmony NVIDIA Tegra 2 USB Device
NVIDIA Harmony USB Mass Storage Device
NVIDIA Harmony Android Composite ADB Interface
The first is listed as connected. The others aren't.
When run adb i get this:
> adb kill-server
> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
No devices are listed.
I have tried many combinations of uninstalling these devices (with Device Manager and with USBDeview). When I reconnect I get prompted to install drivers. I have tried installing at this point, cancelling and then installing in Device Manager, not cancelling so the Plug and Play window stays open and uninstalling with device manager. None of this has worked. Also the device drivers seem to linger on my machine as they seem to auto-reinstall even after I have uninstalled them (I've also tried the suggestion of searching and deleting the .inf and .dlls from C:\Windows -- that didn't work out either).
I have also been careful to make sure adb is not running when I change the drivers. I have tried rebooting the computer and the gTablet after various installs.
The only way I can get the gTablet to appear in "Other devices" is to plug the device in (the PnP window pops up, I leave it open and ignore it). Then I delete the drivers in USBDeview. Then I unplug and replug the gTablet. Now there is one device in "Other devices": NVIDIA Harmony. Problem is, if I right-click "Update driver..." it won't let me install from the Android .inf, it says "The specified location does not provide information about your hardware." and forces me to install "USB Composite device". Once that's installed, two more NVIDIA Harmony devices appear in "Other devices". The first requires me to install "USB Mass Storage Device" (once again won't accept the .inf). The third does allow me to install "Android Composite ADB Interface". That gets me to the point where the drivers are loaded as listed above. But adb still lists no devices.
When I first started trying to set this up I had old drivers for the original HTC android phone installed. I deleted these with USBDeview.
I think that's all the information I have. Please let me know if you have any suggestions, I'd love to get this working.
Thanks!
A real plus would be screenshots, I'm getting a little confused at the device manager window, especially the part where it's supposed to give you the option "let me pick" > "have disk" > locate the .inf > choose the last of the three choices
I'm not getting any of those windows/options. Also, when I uninstall it, unplug the gTab, and plug it back in, it just re-installs the default Tegra driver. Any help?
Right now my device is showing up under "Disk Drives" as "NVIDIA Tegra 2 USB Device", and then also under "Portable Devices" as "G:\"
EDIT: Fixed! (Sorta)
I found another forum that told me that in Device Manager, select "Add Legacy Hardware" from the "Action" menu. After going through there, I was able to complete the steps you told me to. If anybody's having the same problem I had before, I am using Windows 7 64-bit, so that may be part of the problem? I'm not sure. But it's installed now and in Device Manager it's under the "Android Phone" section as "Android Composite ADB Interface".
However this raises a new problem, it has a yellow triangle with an exclamation mark over the icon, and it comes up with the error "Error code 10: Device cannot start".
Any help?
you edited the .inf file to contain the three lines specified, and selected the modified driver when adding the driver, correct? i'll try to add some screenshots for the dev manager section
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Hi,
FYI, one thing to be careful of: In the thread where there's info about adding the 3 lines to the .inf, there's also a full .inf file.
If you try to use the full .inf file, note that it has references to various DLLs, which may, or may not match the DLLs in the driver install directory, so, if you use that full .inf from the thread, you have to adjust those DLL references to the ones for the DLLs you actually have on your machine.
In my case, I found it easier to just add the 3 lines to the .inf that came when I installed the USB driver files from the Android development website, which then worked.
Just an FYI...
Jim
iammuze said:
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Click to expand...
Click to collapse
THIS IS PIVOTAL... This is where I had the hang up. Make sure that you are looking at iammuze's pic here, especially the 2nd image. by default most of us are used to just pointing to the correct directory where we DO have the modified .ini and it grabbed the wrong one. You HAVE to select 'let me pick'
Thank you iammuze for pointing this out. I think that's where most get lost. It haunted me for weeks as I was just 'skinning' through directions and missed this important step!
Just a quick suggestion - instead of trying to hunt around and fix drivers that are already installed and broken, I highly suggest using USB Deview (http://www.nirsoft.net/utils/usb_devices_view.html) which lets you nuke out the old drivers easily on a Windows Vista/7 machine.
I had old ADB drivers from my Nexus One sitting around, and I was unable to uninstall stuff with Device Manager.
Just run USBDeview **as administrator** if you are on Windows Vista/7 and you can uninstall old drivers for USB devices with a single click (in this case, just nuke any old Harmony drivers or other ADB drivers). Then the next time you plug in your G Tab, you should be able to select the proper drivers as suggested in the first post.
doesn't work
So i have also been trying for days and can't get it working right.
Running Windows Vista, have ADB installed, and can connect to other Android devices. I have setup the android_winusb.inf properly, but when I connect my device it shows up in Device Manager as a Portable Device->Tegra.
I have uninstalled the tablet and every other android device using usbdeview as admin
I have searched and destroyed all other usb.inf files.
i am running VEGAn-1.0.5B
No matter what happens, as soon as I plug in the tablet it immediately installs it as a Tegra Portable.
any help is appreciated!
that's very odd, i haven't seen that device description before. it doesn't sound like a vista issue... do you have another computer with vista on it anywhere that you can plug your gtab into? just to see what it reports to dev manager on a super clean system.
Old drivers were conflicting from previous installation attempts for me as well. All is working well once USBDeview was finally able to uninstall the device, however, it took multiple attempts and reboots for it to actually remove them. All is well now, and my Device is connected to the ADB. Thanks Everyone!
Hi, I'm having an extremly annoyning issue with my S8530. I can't seem to make Windows XP SP3 32-bit recognize properly my phone. I have install all the drivers I could find (old, new, from official site, from the undergorund of the internet) and it still gets stuck on detectic USB Serial Port giving just the message that something went wrong and it can't install driver (from auto-detecting devices from Windows). It did install Composit and Modem parts of the drivers but it allways stuck at that part no matter what driver I pre-install, how many restart I do to the PC, how many USB ports I keep chainging, how many USB cables I swap, how many restart I give to the phone. I'm starting going bananananananananananananananananananas.
Any ideeas are greatly apriciated.
Respect Ovidiu
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Renate NST said:
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Click to expand...
Click to collapse
ADB over USB so I can make Kies recognize my phone, wich won't work in Mass Storage. And it should be plug and play (after installing Kies wich installs the drivers or by just intalling the drivers alone). I don't have other machines to trie with Windows 7 (wich allways worked before) and my current PC barelly handles 5 open tabs of Chrome so no Windows 7 options here.
Plug your phone into the Windows box.
Go to Device Manager and find under Properties the VID/PID.
Check the INF file for the ADB driver and see if your IDs are in there.
If not, make a section like all the other sections with your VID/PID in it.
Install the driver.
I'm trying to unlock my mate 8 but when I plug it into my pc it says USB device not recognized. Are there drivers I need to install first? If so where would I find them? I have developer options and enabled USB debugging.
I tried manually installing the driver using these instructions https://www.dc-unlocker.com/how-to-install-drivers-manually but it will not work. It shows up as unknown usb device (device descriptor request failed) and then when I manually install drivers to that usb device it says "windows has determined the driver software for your device is up to date.". This is incredibly frustrating someone please help me out. Can you link me a driver that actually works and automatically involved?
Thanks
please help
If you connect your phone to your pc, especially in Windows, you will notice about Windows asking to run driver downloader. Just run it and it will download the software. Once it is installed, your phone is connected.
Sent from my HUAWEI NXT-L29 using Tapatalk
morxs said:
If you connect your phone to your pc, especially in Windows, you will notice about Windows asking to run driver downloader. Just run it and it will download the software. Once it is installed, your phone is connected.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Hey I downloaded the hisuite from huawei's website and it properly installed the drivers. Thanks for the advice though!
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
hahaha1659 said:
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
Click to expand...
Click to collapse
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
hahaha1659 said:
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
Click to expand...
Click to collapse
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
hahaha1659 said:
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
Click to expand...
Click to collapse
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
hahaha1659 said:
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
Click to expand...
Click to collapse
It was created by a member of this forum, you should be able to find a safe version here somewhere.
Sent from my LGL84VL using Tapatalk