Database Info

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
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 in the link provided by jimcpl, 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.

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 in the link provided by jimcpl, 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
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] Nexus S Root-Windows requests 'Android 1.0' hardware driver (and other weirdness)

Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.

Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928

webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!

haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!

bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders

The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.

jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.

I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid

I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!

Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!

Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S

Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App

Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"

When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work

matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!

thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App

matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!

I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box

[Q] ADB no devices

Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.

Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.

ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.

Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?

it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.

davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.

enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.

Link: USB Driver for T-Mobile SGH-t769 Samsung Galaxy S Blaze 4G

http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe

22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?

Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2

Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.

I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA

Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.

No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.

Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?

Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10

strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?

New TF700T not showing in adb?

Hey everyone,
I've read through the All-In-One guide about how to root the TF700T, downloaded the driver pack, put it into developer mode and enabled unknown sources. When I plugged the device into my computer it was immediately recognized and automatically installed the drivers and I can see it through Windows Explorer and browse the file system.
Unfortunately the device doesn't show in adb and I read through this quote in the guide, "if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)" so I went to the Device Driver and and tried to update the driver with the ADB driver, however, it says it's not compatible.
On the Android device I see the USB mode as Media Device (MTP) and that USB Debugging Connected
In Windows Device manager I see under "Portable Devices" the "ASUS Transformer Pad TF700T" is there and installed without error.
There aren't any device drivers that have a yellow icon indicating they aren't configured correctly.
I had purchased the tablet a few days back and it prompted me for a system update which I did.
I've tried rebooting both my computer and the tablet but it didn't appear to assist.
I'm assuming I'm doing something silly and simple but I cannot for the life of me figure it out.
Does anyone have any suggestions on what I may be doing wrong?
Thanks in advance everyone,
Septurious

Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium

Thanks!
Nebucatnetzer said:
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious

Glad I could help.
Excuse me that I didn't post the link directly it's a pain on the phone.

I had a similar problem. The TF700 was automatically found, and no ADB drivers were installed. I kept trying to uninstall the driver, but it wouldnt let me. I don't have an option to "delete drivers" on uninstall.
When I tried installing "legacy hardware" to force the drivers, it would come up listed under "Samsung" and not Asus. I think I have my drivers all screwed up from previous phones i've had. I took the driver set, and went to another PC (same os, Win 7 ult x64), and had no problem installing all the drivers and rooting.
Anyone have an idea for me? Not sure if I should start going through my sys32 and manually deleting all driver files associated with my tablet.

Fixed.
I had to do this.
http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7
Went through and cleaned up all the old drivers, between the old Samsung Drivers, Motorola Drivers, previous Android ADB drivers. I now plugged in my TF700, and while the ADB shows up as a Samsung device, it shows up on "adb devices", which it didnt before.

Another solution
I tried all listed tips but failed.
ADB driver was installed automaticaly after enabling USB-modem on my TF700.
Now android device chooser showing device

for hours i tried it! no i know why it didnt work!
turn off windows firewall!!! DD maaaaaan

Septurious said:
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Click to expand...
Click to collapse
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?

GBDias said:
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
Click to expand...
Click to collapse
Windows 8?
Try disabling driver signature verification.
Sent from my DROID4 using Tapatalk