Yeah, its another 'ADB not working on device xxx' thread.. but this one really has me stumped.
Device in question is a TF101, PC in question runs Windows 7 64-bit.
PC has been used successfully to develop android apps. for a Samsung S Plus, with the entire toolchain working.
Same PC, running VMWare, virtualizing XP (32-bit), has also been used to develop/debug with the TF101.
Now the problem. Natively (without VMWare), I have been completely unsuccessful getting the TF101 to be recognized by ADB.
What has been tried:
- TF101 USB drivers from Asus
- TF201 USB drivers from Asus (which also include the TF101 drivers from the look of the .inf files)
- Hand-edited .inf file from the standard android ADB driver
- Adding the VID (0x0b05) to adb_usb.inf
- Uninstalling (and deleting the driver) for anything related to android devices (Samsung, and Asus)
So what happens is that the device does appear in device manager, with 'USB Debugging' checked on the Android device.
With one of the driver combinations I end up with 'Android Composite ADB Interface' in Device Manager, but for some reason its under a 'Samsung Android Phone' Folder, this may well be part of the problem.
No matter what I try, 'adb kill-devices/adb usb' always shows 'error: device not found'
I am two solid days into this now, after reading just about every TF101/ADB thread that google knows about.
Anyone else experienced this?, and might know how to resolve it?
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
FWIW, I had the same issue. I installed the USB drivers from Asus and could never seem to get ADB to "see" the TF101.
So I ripped them out and installed the full ASUS desktop PC suite from their website. ADB now sees my TF101 just fine. I uninstalled the suite after I had the connection working and ADB still connects to my TF101 without issue. The Transformer PC suite is on the same download page as the stand alone driver.
If you can't find it, PM me and I'll get back to you with a link.
Col.Kernel said:
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
Click to expand...
Click to collapse
I too was using ADB already on my N1 but couldn't make it work with the TF.
After reading and following directions on that thread I got it working.
He might not need instructions to set up ADB from scratch but there's good infos about the Asus PC Suite.
Step 7
Basically same as what you just posted and same as what I did to get it working.
I can confirm that too that installing ASUS SUIT works better than just installing drivers, I don't know why but it does. It's the same with my phone. Sometimes installing usb drivers do not work but when I install Samsung kies then somehow that works better even though it includes the same drivers I am installing as stand alone which do not with properly.
Sent from samsung vibrant
Same thing happened to me had to buy a new cord.... does the computer recognize it at all
Sent from my Transformer TF101 using Tapatalk
im not sure if it would help but everyonce in a while ill have a hard time with my adb connection and ill start up wireless adb and can conect fine from that. i dont know why i think in wireless you use ip address on wifi so it might recognize and connect different.. of course this depends on if you want to use it and is alos hardware dependant mainly wifi.
Related
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.
I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.
I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120
What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..
Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.
Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.
hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.
I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?
xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium
Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.
I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.
I have been trying to get my Tf101 to connect to ADB for a good 6+ hours now. I have installed the asus software and drivers, I have installed the drivers that I found here for the APX, ADB, ext stuff and I still cannot connect. No matter how many times I kill and start the ADB server or try to use the ADB exe from the SDK or use the one from viper mod it's just says
List of devices attached
Nothing else is displayed.
got device manager to now have an android device tab with the asus transformer adb interface under it. still no luck.
BTW, window 7 pro x64.
Solved, apparently the tablet needs to be in USb camera mode.
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
I did remove the SM Bus Controller from device manager and then re-installed the LG device driver. It did not attempt to reinstall SM Bus drivers, but instead installed MTP drivers successfully. I had high hopes after that, but it's still not working. Sigh.
bgibson72 said:
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
Click to expand...
Click to collapse
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
elijah420 said:
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
Click to expand...
Click to collapse
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
bgibson72 said:
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
Click to expand...
Click to collapse
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
elijah420 said:
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
Click to expand...
Click to collapse
It's cool, thanks anyway. Just trying to simplify things. Don't ask why I thought the OEM's software was gonna solve that, lol.
Well, tbf, even though I don't use it (simply because I dislike vendor lock in - owncloud or a sftp session is mostly hardware agnostic.) I do understand the idea that one should expect the **** that come on the phone to work properly. It *should* be a selling point - 'our apps work for their stated purpose!'